List of all access errors?

R

Roland

Hi,

I am accessing a database from a visual c++ application via ADO.
Everytime I open or close the database, the errors collection of my
connection object contains the following MSAccess error:

SQLState: 3811
Native Error: 249 761 507
Source: Microsoft Jet Database Engine

Opening and closing the database works anyway, so I think the error is
not serious. I tried to lookup the error number, but couldn't find a
comprehensive list of all possible native access errors.

Is there a list of all access errors? Does anybody know what this error
means?

Thanks, Roland
 
G

Gijs Beukenoot

From Roland :
Hi,

I am accessing a database from a visual c++ application via ADO.
Everytime I open or close the database, the errors collection of my
connection object contains the following MSAccess error:

SQLState: 3811
Native Error: 249 761 507
Source: Microsoft Jet Database Engine

Opening and closing the database works anyway, so I think the error is
not serious. I tried to lookup the error number, but couldn't find a
comprehensive list of all possible native access errors.

Is there a list of all access errors? Does anybody know what this error
means?

Thanks, Roland
Click to expand...

3811 -- Attempt to open the datasbase with the requested record level
locking failed; page level locking will be used

What this means is that if in your database you run the following code
after it is open:

Set con = New ADODB.Connection
con.Provider = "Microsoft.JET.OLEDB.4.0"
con.Properties("Data Source") = CurrentDb.Name
con.Properties("Jet OLEDB:Database Locking Mode") = 1 ' use 0 for
page level check
con.CursorLocation = adUseServer
con.Open

and the database was not in the mode you asked for tht you will see one
of those warnings in the NativeError property, right in
con.Errors(0).NativeError.

(from http://blogs.msdn.com/michkap/comments/482694.aspx)
 
R

Roland

Hi Gijs,

wow, thanks for the quick response, it helped me alot. Exactly the kind
of information I was looking for. I will check that as soon as I am back
in the office.

Thanks again,

Roland
 
Top