"nate" wrote:

> I have an Access 2003 database I've been creating for the past three weeks,
> and all of a sudden last week, when I tried to work on it, I got an error
> message saying I didn't have permission to view the tables.  I'm not sure
> what caused it, or whether the database itself or workgroup file is causing
> the problem, but it appears that no users, even admin, have any permissions
> on any objects.  The groups I created with the Security wizard are no longer
> in the workgroup file, and the owner (which had been me) for every objetc is
> now set to "<unknown>".  This was a db stored locally, and I was the only one
> who ever opened it.
>
> Is there anything I can do to get my work back?  I can't export everything
> to a new database because I don't have permission.  I've been looking for
> software, and most get user passwords, which is useless for me, because there
> are no passwords, I need permissions.  One piece of software (Access
> Recovery) seems to be able to do it, but it costs $400.  Are there any other
> possible solutions?  And, perhaps more importantly, why did this happen, and
> how can I prevent it from happening when it matters most, when we are
> actually using it to collect data?
>
> Any help would be greatly appreciated.

"'69 Camaro" wrote:
> This means that you used the wrong workgroup file to open this database
> file, and it means that you did not properly secure the database (since you
> wouldn't even be able to open the file if it were secured).  If you don't
> remember the path and file name to your secure workgroup, search your hard
> drive (and possibly the network) for *.MDW and test each of these workgroup
> files to determine which one is the correct one.  (The default is
> System.MDW.)  Once you find the correct one, join it, create a new database
> file and import all the objects from the current database into it.  The user
> you log in as will be the owner of all these imported objects.
>
> It's a common practice to always be joined to the default workgroup file,
> but use Windows shortcuts to open secured databases to keep from being
> prompted for user name and password when opening any database file.  For
> example:
>
> "C:\Program Files\Microsoft Office\OFFICE\MSAccess.exe" "C:\Data\MyDB.mdb"
> /wrkgrp "C:\Data\Secure.mdw"
>
> > why did this happen, and
> > how can I prevent it from happening when it matters most
>
> One must be aware of which workgroup one is joined to.  It's common practice
> to be joined to the default workgroup, but use Windows shortcuts to open
> secure databases so as not to be prompted for user name and password when
> opening databases.
>
> HTH.
> Gunny