The sql.log file is over 5M. There are no references to foreign keys
anywhere in the log file. I noticed the following:
Orders 138:118 ENTER SQLExecDirect
HSTMT 0x09072230
UCHAR * 0x040f10f0 [ -3] "SELECT
Config, nValue FROM MSysConf\ 0"
SDWORD -3
This failed because my Postgres database does not have this table. Any idea
what MsysConf, what it contains, or how to create it? Could this have
anything to do with my Access subform problem?
Thanks, Michael
-----Original Message-----
From: Byron Nikolaidis [SMTP:byronn@insightdist.com]
<mailto:[SMTP:byronn@insightdist.com]>
Sent: Thursday, February 25, 1999 2:12 PM
To: Michael Davis
Cc: 'pgsql-interfaces@postgreSQL.org'
Subject: Re: [INTERFACES] Foreign Keys
Michael Davis wrote:
> I have created the following trigger on the parent/master
table
(orders):
>
> CREATE TRIGGER Orderlines_fkey
> BEFORE DELETE OR UPDATE ON Orders FOR EACH ROW
> EXECUTE PROCEDURE check_foreign_key ();
>
> check_foreign_key() actually deletes rows from the
orderlines
table when
> every a row is deleted from orders. This triggers works
great.
Access,
> however, is still not recognizing the foreign key
relationship
between
> orders and orderlines. Any other suggestions?
>
> Thanks, Michael
>
Yeah, there is more we can try. First of all, we need to verify
that Access
is actually calling SQLForeignKeys. Can you get a "trace" log of
the
session? This would be the "sql.log" file which contains all api
calls to
odbc. Make sure the file is clear beforehand. Then run the test.
Quit
Access, turn tracing off and there's your logfile. You can send it to me.
It might also be helpful to have the commlog file (produced by the
driver)...usually "psqlodbc.log". It may have a process id number
appended
to the filename so make sure you get the right one.
Byron
