ADO- Open Connection error after adding security

[CrystalJim]

Hello everyone,

Stats: Access 2003 (using 2000 file format), Windows 2003, XP-Pro, all files
reside on shared server - not local machine.

I have created an Access App that used an ADO connection to return records
from the database. This was working fine until I setup security.

At first, I was getting an error saying I did not have permissions to open
the database with the error occurring when the code got to the
"connection.open" line.

So I added in the password and user id. That failed. I Googled the error
message and found that the password needed to be set as a connection
property.
So, I rewrote the code and set the userid and password using:

connection.properties(user id) = "userid"
connection.properties("Password") = "pan1010x"
or this variation from the Google post –
connection.properties("Jet OLEDBatabase Password") = "pan1010x"

I now get this error:
Run-time error '-2147217843'

Cannot start your application. The workgroup information file is missing or
opened exclusively by another user.

The workgroup file is not missing as I can open the database. The file is
not opened by another user as I am the only user.

Security wise the admins group and users group have no permissions. Two new
admin accounts were created (one is the owner of all objects) and assigned
ALL permissions on the database, both as a user and as a member of a group
that has ALL permissions. There is also a user whole has all but security
permissions (not a member of the new admin group) so does not open the
database exclusively.

This error occurs no matter which user logs on to the database.

Is this a design feature? If not what am I missing?

Thanks,

Jim

aka - CrystalJim

 

[Alex Dybenko]

Hi,
I think you also need to specify system database in this case, like a
connection property or as a part of connection string (see
http://www.connectionstrings.com/):

System database=c:\mysystem.mdw

--
Best regards,
___________
Alex Dybenko (MVP)
http://alexdyb.blogspot.com
http://www.PointLtd.com

 

[CrystalJim]

Thanks so much. I remember that sight from a prior life.

This morning, when I went to add the code for the system database, after
opening the database using the same admin user that gave me an error, I tried
running the procedure again.

Now it works!!!! No changes made to the program. The only thing that
happened was the auto update ran last night (not by choice - lost a days
worth of Profiler info) and restarted the computer when done.

I'll make the change anyway just to play safe.

Thanks again.

Jim