MS Access ULS stopped working after a power cut / blackout

[Franc Sutherland]

Hello everyone.

I've set up an access database on a small server. It is split front and
back end. The back end is on the server, and the front ends are on local
PC's. The security mdw file is on the server in the same location as the
back end. One front end was kept out of the ULS setup and connects fine to
the server back end from its PC located front end.

There was a power cut / blackout and now only the PC which is outwith the
ULS works. The others all have the "you do not have permission to
access....error 3033" warning coming up.

Have the front-ends stopped communicating properly with the workgroup
security mdw file?

Regards,
Franc.

 

['69 Camaro]

Hi, Franc.

One front end was kept out of the ULS setup and connects fine to
the server back end from its PC located front end.

If any user can connect to a secure database without joining the secure
workgroup, it means that the database isn't secured, because at least one
step was skipped. You will have to redo your security. For more
information on implementing User-Level Security, download and study the
Security FAQ from the following Web page:

http://support.microsoft.com/?id=207793

Practice on a copy of your database before implementing security on a
production version.

Have the front-ends stopped communicating properly with the workgroup
security mdw file?

The users aren't joined to the secure workgroup any longer. It's likely
been reset to the default workgroup when Windows recovered from the power
off disaster, but each user can check which workgroup he is currently joined
to by using the Workgroup Administrator. It's recommended to remain joined
to the default workgroup and use a Windows shortcut to open any secured
database so that the user only has to sign in for the secured databases.

First, have each user join his default workgroup (if he isn't already) with
the Workgroup Administrator. Then create and distribute a Windows shortcut
that opens the secured database while pointing to the secured workgroup so
that the user will be joined to it for the current session only. Use the
following syntax for the shortcut's target (all one line):

"<Full path to Office>\MSAccess.EXE" "<Full path to DB>\MyDB.MDB" /wrkgrp
"<Full path to secure workgroup>\Secure.MDW"

HTH.
Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips and tutorials.
Blogs: www.DataDevilDog.BlogSpot.com, www.DatabaseTips.BlogSpot.com
http://www.Access.QBuilt.com/html/expert_contributors2.html for contact
info.

 

[Franc Sutherland]

Dear Gunny,
Thanks for your quick reply. There's always so much more to learn!!
With your advice I have found a temporary fix and also have a long term
resolution. Can't ask for better than that.
Regards,
Franc.

 

['69 Camaro]

You're welcome! Glad to help!

Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips and tutorials.
Blogs: www.DataDevilDog.BlogSpot.com, www.DatabaseTips.BlogSpot.com
http://www.Access.QBuilt.com/html/expert_contributors2.html for contact
info.