--- Aaron Spike <sauron@mlc-wels.edu> wrote:
> > So, for you this should "just work". I don't have
> an
> > answer, but maybe someone else can suggest it.
>
> Well it didn't just work. Until I dropped and
> recreated the table and
> copied the data back in. Now it works fine. Its
> almost like the
> driver knew that the index was on the first field
> and the last two
> fields.
>
> Problems and fixes aside can anyone offer more
> information on how the
> pgodbc driver and access decide whether or not to
> present the "Select
> Unique Record Identifier" dialogue when linking
> tables?
I suspect that is up to the ODBC driver. Anybody feel
like hunting through the code for "SQLPrimaryKeys()"?
;-)
>
> > If you don't have logging enabled, you may want to
> try
> > that for a while; there may be some clues in
> there.
>
> Logging with the odbc driver or on the server?
Driver (MyLog) logging will tell you exactly what the
driver is sending to the server, and what it is doing
with what it gets back. But that is extremely verbose
and hard to follow. But may be indispensable if you
are having a problem.
>
> > BTW, I suggest you reconsider your use of a
> composite
> > primary key. The fact that they are supported
> doesn't
> > make them a good idea.
>
> Not my choice actually, but after working with them
> for some time I
> they have grown on me.
>
> Aaron Spike
__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free web site building tool. Try it!
http://webhosting.yahoo.com/ps/sb/
