RE: [INTERFACES] Foreign Keys

Here is the psqlodbc.log file. The first time the form opens, it correctly
opens the first rentalorder. I immediately moved to the new record in
Access which opens a message box with an ODBC error (no description). I the
blank rental order looks okay but the rental order lines records all have
errors. Even if I move back to a valid record, the order lines will show
only errors.

<<psqlodbc_270.log>>

-----Original Message-----
From: Byron Nikolaidis [SMTP:byronn(at)insightdist(dot)com]
Sent: Tuesday, March 02, 1999 12:52 PM
To: Michael Davis
Cc: 'pgsql-interfaces(at)postgreSQL(dot)org'
Subject: Re: [INTERFACES] Foreign Keys

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