Re: Users Can't Open Access Database Security Or Corruption ??

<davstar.f@xxxxxxxxx> wrote in message
news:1170036684.747386.254900@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

I have a problem where I copied the front end of an application to the
local office server. If a user opens the front end they get an
error :

Why did you copy the FE to the server? Each user should have their own copy
of the FE on their computer. Just put the backend on the server.

"Database is in an unexpected state; Microsoft Office Can't open it."

This Database has been converted from a prior version of microsoft
office access by using the DAO Compactdatabase method instead of the
convert database command on the tools menu (database Utilities
submenu). This has left the database in a partially converted state.

Was this database ever converted from an earlier version?

If I open the same database it opens with no problems.

All users and myself are using MS Access version 2003 build
11.6566.8107 SP2

Does anyone know what is going on??????
Help or advice would be greatly appreciated

Might you have copied the FE to the server, while it was in use? That's not
a good idea. See if you can copy it back to your local computer, and then
compile, save, and compact it there.

The workgroup was setup so that it was not neccesary for the users to
login. Initially I used a workgroup file with a development group and
the admin group.

The admin group was stripped of the usual design change permissions
and the queries were set to run with owners permission.

This way the user opens up the database with the default system.mdw
workgroup file and has the permissions of the admin goup.

I think you are mixing up the users/groups. I assume you mean the Admins
group, and not some group you created called admin. Also you wouldn't need
to create a development group, just use the Admins Group (since it is
different in all mdw files). It's the Users Group and the Admin user that
are in common. So what you'd want to do is give permissions to the Users
Group, and then they can use the standard system.mdw workgroup. Or did you
mean Admin User?

Anyway, try the repair locally. Ensure it's not in use when you copy it to
the server (delete any ldb files you see there). Again you should be giving
a copy of the FE to each user on their computer.

--
Joan Wild
Microsoft Access MVP


.

Relevant Pages

  • Re: User Level Security Malfunction
    ... menu, the Users group has no rights to open the database, and it also ... I first create a blank secured file that I ... Remove Admin from Admins group ... Remove all permissions to "new" objects from Admin ...
    (microsoft.public.access.security)
  • RE: copy permissions from one user to another?
    ... THIS STORED PROCEDURE GENERATES COMMANDS ... -- ADD USER TO SERVER ... -- CREATE TABLE TO HOLD LIST OF USERS IN CURRENT DATABASE ... -- SET COMMAND TO FIND USER PERMISSIONS HAS IN CURRENT DATABASE ...
    (microsoft.public.sqlserver.security)
  • Re: Setting up Linked server to MsAccess
    ... (it should 'map' all users to use Admin with no password for the linked ... that will list all the linkedsrvlogins with their ... At the database level I have added my Server login ...
    (microsoft.public.sqlserver.security)
  • Q: low permission cannot convert from A97 to A2000/2003
    ... A97, but the database is sent out and used by contractors (user permissions) ... The admin user has full privileges. ... The problem we are having is converting the database from A97 to 2000+. ...
    (microsoft.public.access.security)
  • Re: Restored Server but SharePoint refusing admin access
    ... > SID/BID or remove the user from the database and add it again. ... >, In SQL Configuration Manager go to SQL> Server ... > you had) you cannot access the database from that account. ... > newly added administrator account (for me, since I added a new admin ...
    (microsoft.public.windows.server.sbs)
Loading