Message-Id: <36DC4164.C461E1C2@insightdist.com>
Date: Tue, 02 Mar 1999 14:52:04 -0500
From: Byron Nikolaidis <byronn@insightdist.com>
Mime-Version: 1.0
To: Michael Davis <michael.davis@prevuenet.com>
Cc: "'pgsql-interfaces@postgreSQL.org'" <pgsql-interfaces@postgreSQL.org>
Subject: Re: [INTERFACES] Foreign Keys
References: <93C04F1F5173D211A27900105AA8FCFC145218@lambic.prevuenet.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit


Michael Davis wrote:

> I have narrowed the problem down a little.  Here is what I have discovered
> so far:
>
> -       sql.log (odbc trace facility) has no references to primary or
> foreign keys
>
> -       if I open the form on an exising record, it works great
>
> -       if I open the form on a new record, an error occurs in a select
> statement that basically locks up the subform
>
> -       the error occurs on "select orderlineid from orderlines where
> orderid = NULL"  the null is the result of being on a new or blank record.
> Access gets the orderid of the current record, it is null.  Access gets all
> orderlineids associated with the orderid.  This fails on the new record.
> When the form is on a valid record, Access then gets the orderline record
> for each orderlineid returned by the previous statement.  This seems to be a
> long way around getting data, but I don't have any control over this
> interaction.
>
> It appears that I cant add new records using Access97 with PostgreSQL as my
> database engine.  Has anyone used Access97 or other similar front end tools
> to interface with a PostgreSQL database?  Any suggestions on what I might
> try next to work around this problem?
>
>

Logs, logs, logs (see my last response).  I don't know how else to put it!

Its next to impossible to figure things out without the logs.

Byron