Problem is when connection is closed. You will get AV. With Borland driver it will try to connect. It is annoying in design time. Probably it is problem with other procedures like GetFieldNames, GetProcedureNames, GetIndexNames. I have also Oracle, MySQL dbx driver and I have the same problem. All drivers are latest versions.
With Regards,
Radovan Antloga
Bug with GetTableNames
-
- Posts: 18
- Joined: Wed 25 Jan 2006 09:28
Bug with GetTableNames
When trying to build sample program I found that it is not a problem with your DBX drivers. Sorry for that !!!
I have component that use dbx drivers. It worked ok with D7 but is not with D2007. In some situation uses GetTableNames but in some creates sql for query and gets metadata. Interesting is that first time it works with SQLConnection.Connected = False but second time it gets AV. I can reproduce it every time. But as I say it si not your problem as I later found out it is same problem with Borland driver.
I have component that use dbx drivers. It worked ok with D7 but is not with D2007. In some situation uses GetTableNames but in some creates sql for query and gets metadata. Interesting is that first time it works with SQLConnection.Connected = False but second time it gets AV. I can reproduce it every time. But as I say it si not your problem as I later found out it is same problem with Borland driver.