G
Guest
Ladies and Gentlemen:
I’m having a problem with ULS similar to the one discussed in one of the
blows below (ULS Flaw?). I’m running MS Access 2003 on Windows XP. I’ve
already created all the groups and users, and have assigned all the
permissions; all under a new workgroup. Lastly I ran the ULS Wizard which
created the .bak file and gave me the nice summery report at the end. I
checked the ownerships, to include that of the database itself, and none of
the objects are owned my Admin.
That said, I can still sign in to a different workgroup (i.e. the original
system.mdw file) and can access the file without any challenge. Did I miss a
step in securing the file? Is there a way to verify that the file is
actually secured? Please help.
A-Mart
I’m having a problem with ULS similar to the one discussed in one of the
blows below (ULS Flaw?). I’m running MS Access 2003 on Windows XP. I’ve
already created all the groups and users, and have assigned all the
permissions; all under a new workgroup. Lastly I ran the ULS Wizard which
created the .bak file and gave me the nice summery report at the end. I
checked the ownerships, to include that of the database itself, and none of
the objects are owned my Admin.
That said, I can still sign in to a different workgroup (i.e. the original
system.mdw file) and can access the file without any challenge. Did I miss a
step in securing the file? Is there a way to verify that the file is
actually secured? Please help.
A-Mart