One of my clients has recently migrated to Office 2007, and I have run into a few issues with the new ODBC driver provided for MS Access. I am using the driver ACEODBC.dll, version 12.00.6211.1000
1. From my testing in V7 and V8, it appears that when using the generic driver, and the database is located in the same folder as the QlikView file, some type of path must be specified, or the driver will search in C:\ for the database.
For example, if my QV document and database are both located in D:\Customers\ABC
ODBC CONNECT TO [MS Access Database;DBQ=my_database.mdb;
will return an error "Not a valid file name." However,
ODBC CONNECT TO [MS Access Database;DBQ=..\ABC\my_database.mdb;
will work fine.
2. When trying to load from a fairly large (about 500K records and 30 fields) table in the database, one of my users will take 60 minutes consistently. Another user will take 5 minutes (about the time it took with Office 2003). Both users are using QlikView 7.52 (I am about to try V8), have 2 GB RAM, and the same general software config. Obviously, something is different between the user configs, but I have not been able to determine what the difference is yet. I was wondering if anyone has seen this, and what they did to correct it.
