> How about creating a second copy of query and preparing it, then
> scan the column names from that, then unprepare it etc. I presume
> this would add some overhead to the process, but it is just a
> suggestion.

It would certainly solve the parsing problem (or at least hand it on
to IB/FB).

Actually the more I think about it the better I like it. It would
only be necessary when..
KeyLinksAutoDefine is true AND
not explicit KeyLinks are given AND
the primary key fields appear (via the simple POS test)
to be in the select SQL.

in only that cirumstance do we need to validate that the fields are
properly and fully matched - so we create a simple cursor or dsql and
prepare it and test the resulting fields.

It may be a noticable overhead, but it would be reliable. And if
people want to avoid the overhead they define their own keylinks.

Disclaimer: It could be that I like the idea because I dont use
AutoDefine, so I know I wont be impacted by change ;-)

> (Be gentle with me !)

How was that :-)


--
Geoff Worboys - TeamIBO
Telesis Computing