One of my customers has an Access database with table fields which contain question marks.
Yes I know what you're saying, who uses '?' in field names, customers of course !
When I try to run a uniquery containing these field names it gives and error and the query fails.
Using the same SQL with ADOQuery OleDb Driver, works perfect.
Go into MS Access and query the table, also works perfect.
Any idea what's causing this ?
Thanks !
Access Query error - Field names containing question marks
I realised after I posted this that Unidac uses ODBC driver for Access which seems to be the cause.
I'm not surprised, in my 25 years of programming I have never found any ODBC driver to be reliable for any database. Always use Oledb if possible, much better !
Do Devart have any plans to add Oledb as a Unidac provider ?
I'm not surprised, in my 25 years of programming I have never found any ODBC driver to be reliable for any database. Always use Oledb if possible, much better !
Do Devart have any plans to add Oledb as a Unidac provider ?
Hello,
I checked UniDAC behaviour when working with MS Access tables that have the '?' symbol in their names and did not encounter any errors – tables are opened successfully, and data and field names are displayed correctly.
Please send us the database file to alexp*devart*com and specify versions of your UniDAC and IDE.
I checked UniDAC behaviour when working with MS Access tables that have the '?' symbol in their names and did not encounter any errors – tables are opened successfully, and data and field names are displayed correctly.
Please send us the database file to alexp*devart*com and specify versions of your UniDAC and IDE.
Hello,
Thank you for the information. We have reproduced the problem, however, this problem is conditioned by the specifics of the ODBC driver and this behavior can only be changed on the level of the ODBC driver.
P.S. We shall consider a possibility of implementing the OLE DB support in our products in future.
Thank you for the information. We have reproduced the problem, however, this problem is conditioned by the specifics of the ODBC driver and this behavior can only be changed on the level of the ODBC driver.
P.S. We shall consider a possibility of implementing the OLE DB support in our products in future.