TADOSession.GetTableNamesForConnection
We have made some minor modifications to the source code of RB to cater
for some unique requirements we have. However on porting these changes
between 11.01 and 11.02 I have found a "problem" which I am not sure if
it's a bug or not.
The GetTableNamesForConnection procedure in the TADOSession class which is
new in 11.02 always includes the owner name in the table name which didn't
use to happen in the past.
This means when checking for table names in daSQL, which was the original
change I was applying, matches weren't being found because the table names
I was supplying did not have the owner name at the beginning.
This change has obviously been done intentionally but I cannot understand
the reason behind it.
Paul
--- posted by geoForum on http://delphi.newswhat.com
for some unique requirements we have. However on porting these changes
between 11.01 and 11.02 I have found a "problem" which I am not sure if
it's a bug or not.
The GetTableNamesForConnection procedure in the TADOSession class which is
new in 11.02 always includes the owner name in the table name which didn't
use to happen in the past.
This means when checking for table names in daSQL, which was the original
change I was applying, matches weren't being found because the table names
I was supplying did not have the owner name at the beginning.
This change has obviously been done intentionally but I cannot understand
the reason behind it.
Paul
--- posted by geoForum on http://delphi.newswhat.com
This discussion has been closed.
Comments
request to support@digital-metaphors.com and we can email it to you.
The enhancement to TADOSession.GetTableNamesForConnection was made to
support the case in which the DataDictionary.UserTableOwnerName is true. It
should not affect your existing setup, once the patch is applied.
--
Nard Moseley
Digital Metaphors
www.digital-metaphors.com
Best regards,
Nard Moseley
Digital Metaphors
www.digital-metaphors.com