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

  • Thread starter Thread starter davstar.f
  • Start date Start date
D

davstar.f

Hi folks,

It was suggested I repost this problem here. Please don't yell out
about multi posting.

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 :


"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.


Here is the catch


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


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.


When I need to make changes I use the development.mdw workgroup file
and then login as the developer to make design changes. This method
is described in the Microsoft security fact file and I have used it
before, in fact I am using the same workgroup for the developer that I
have used in previous projects.





Previous Responses


Tom Wickerath View profile

Hi Davstar,

I don't know the answer to your question (I'm not a fan of ULS),
however,
I'd like to suggest that you consider reposting your question in the
newsgroup Microsoft.public.access.security. Here is a link to that
group
using the Web interface:


http://www.microsoft.com/office/community/en-us/default.mspx?
dg=micro...


Make sure you mention that you've already posted in MPA, so that you
don't
get accused of multi-posting.


Good Luck,


Tom Wickerath
Microsoft Access MVP


Joseph Meehan posted this response

If you are able to open the database directly without referencing a
workgroup file, then it does not have user level security or even the
more
basic security.

I seem to recall that error message from someone else
recently .... OK
I'm back. Make sure that the users are using the same workgroup file
as you
are. You can usually find it by looking at the start up string on
the
shortcut if you are using one. It should, hopefully be located on
the
shared server, not one on you own machine.


I also noted someone suggesting that not having the same updates
could
be a problem as well.
 
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 :
Click to expand...

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.
Click to expand...

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
Click to expand...

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.
Click to expand...

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.
 
Back
Top