SQL vs. Access and ODBC
-
I have a program I'm working with (VB :~ ) which accesses it's data via ODBC and an Access database. The Access database is currently in 97 format because I had certain strange problems when it was in Access 2002 format, namely updating records and then finding it had written blank fields to the database etc. These problems disappeared with a Access 97 file. I've recently tried to let this program talk to a SQL server via ODBC which works perfectly, except that it displays the same anomalies as Access databases newer than 97. My suspicion is that the ODBC driver is outdated. Does anyone know if that is possibly the problem, and if so how I can update it. If not, what can it be? TIA :) Paul
-
I have a program I'm working with (VB :~ ) which accesses it's data via ODBC and an Access database. The Access database is currently in 97 format because I had certain strange problems when it was in Access 2002 format, namely updating records and then finding it had written blank fields to the database etc. These problems disappeared with a Access 97 file. I've recently tried to let this program talk to a SQL server via ODBC which works perfectly, except that it displays the same anomalies as Access databases newer than 97. My suspicion is that the ODBC driver is outdated. Does anyone know if that is possibly the problem, and if so how I can update it. If not, what can it be? TIA :) Paul
whats operatin system you use? 1.)Access 2002 is perfect than 97 no argument for it,this can be the link u using(ODBC) 2.)why u not use oledb connection string,its perfect work with vb and access,sql server 3.)how you update records? r u sure u not update any null value to fields
-
whats operatin system you use? 1.)Access 2002 is perfect than 97 no argument for it,this can be the link u using(ODBC) 2.)why u not use oledb connection string,its perfect work with vb and access,sql server 3.)how you update records? r u sure u not update any null value to fields
Windows XP SP2. The ODBC driver for SQL is version 2000.85. 1) huh? 2) yes, I'm considering changing that from the current method, which is using MS ADO data control 6.0 3) by binding text fields to the correct fields in the DB and calling adodc.Update, I've checked for null field entries, there aren't any, also this problem only occurs after the Primary Key has hit 400 (it appears :confused: can't see anything else that's consistent on failure) Paul
-
Windows XP SP2. The ODBC driver for SQL is version 2000.85. 1) huh? 2) yes, I'm considering changing that from the current method, which is using MS ADO data control 6.0 3) by binding text fields to the correct fields in the DB and calling adodc.Update, I've checked for null field entries, there aren't any, also this problem only occurs after the Primary Key has hit 400 (it appears :confused: can't see anything else that's consistent on failure) Paul
-
whats operatin system you use? 1.)Access 2002 is perfect than 97 no argument for it,this can be the link u using(ODBC) 2.)why u not use oledb connection string,its perfect work with vb and access,sql server 3.)how you update records? r u sure u not update any null value to fields