M
Maury Markowitz
After some experimentation last night I changed our connection string to
avoid using ODBC. The string used to be:
"ODBC;DSN=OurServer;Database=OurDB;UID=;PWD="
And I changed it to:
"Provider=sqloledb;Data Source=OurServer;Initial Catalog=OurDB;Integrated
Security=SSPI;"
Everything seemed to work OK, but I didn't test it fully. When new rows are
entered into tables with auto-id's, and we have lots of those, Access returns
an error about not being able to fetch the identity:
"Identity cannot be determined for newly inserted rows."
Can anyone suggest why this might be happening. I got the string right from
connectionsstrings.com, and like I said, everything else seems to work fine.
Maury
avoid using ODBC. The string used to be:
"ODBC;DSN=OurServer;Database=OurDB;UID=;PWD="
And I changed it to:
"Provider=sqloledb;Data Source=OurServer;Initial Catalog=OurDB;Integrated
Security=SSPI;"
Everything seemed to work OK, but I didn't test it fully. When new rows are
entered into tables with auto-id's, and we have lots of those, Access returns
an error about not being able to fetch the identity:
"Identity cannot be determined for newly inserted rows."
Can anyone suggest why this might be happening. I got the string right from
connectionsstrings.com, and like I said, everything else seems to work fine.
Maury