OleDB for MS Access - Help!

[Dave Martin]

I am working on a project that is giving me trouble. It
has to be done quickly. It is being written in C# and I
am totally new to C#.

I need to update an MS Access database application that
was created by a third party developer that is no longer
in business. In other words there is no one there I can
turn to for help.

My first set of code gave me every indication of having
updated the data table successfully -- even returning a 1
to show that one row was updated. But when I went to the
table to verify, no changes had taken place.

I assumed that this was security related -- that "whoever"
the system thinks the program *is* does not have rights to
make the change.

So I tried to add security parameters to the connection
string. But then I got the error message: "could not find
an installable ISAM".

A net search convinced me that maybe my syntax was wrong,
so I tried to build a connection string by letting Win
2000 do it (create file.udl, left click, select
propertiesrovider,select MS Provider for ODBC
services...). The result of using this new cs was the
same message.

I am stuck. Do I have a version problem with my OleDB
drivers? Is my syntax still wrong?

Here is the system-built connection string with uid/pw
removed:

Provider=MSDASQL.1;Password=xxxxxxxx;Persist Security
Info=True;User ID=xxxxxxx;Extended Properties="DSN=Access
Files;DBQ=I:\IMS\Data\ImsData.mdb;DefaultDir=I:\IMS\Data;Dr
iver=odbcjt32.dll;DriverId=281;FIL=MS
Access;MaxBufferSize=2048;PageTimeout=5;PWD=xxxx;UID=admin;
"

Note: I removed the outer level server login arguments in
the version I inserted into the app, because the final
connection string is used on the server itself and does
not need it. The Access uid and pw were retained.

Thank you

Dave Martin
NASSCO

 

[Joey Powell]

I am working on a project that is giving me trouble. It

I would use ADO.net. Make sure you have MDAC loaded on the box.

 

[Steve Parker]

Dave,

Did you perhaps begin a transaction and not commit it?

Steve