Privelages

[Matt]

I just upgraded to 2007 from 2003. I am attempting to use the package wizard
to create an install cd for my database. First off, the database was split
before the upgrade, and I did convert the FRONT END to an accdb, but the BACK
END is still listed as an mdb. Everything went smooth, clear through
deployment, except that when I try to open the deployed file, it says I do
not have privelages to access the BACK END file. The back end file is on the
server, with full permissions to all users, since anyones ability to change
anything is handled inside of Access. I read that user level security is not
used in 2007, but was set up on my databse in 2003 file format. Any help
would be greatly appreciated, and if I left anything out, let me know and I
will disclose it. Thanks in advance, Matt.

 

[Tom van Stiphout]

On Thu, 27 Mar 2008 14:18:00 -0700, Matt

Your shortcut should still be essentially the same as in A2003,
including the /wrkgrp switch. Did you not notice the normal login
dialog was not coming up anymore?

-Tom.

 

[Matt]

I did include the /wrkgrp switch. I am not getting far enough in on any of
the workstations to get any dialog, just the error message that pops up.
Something I left out that's probably pretty important is the fact that this
database is being packaged with the runtime files. No other workstation is
running this database through a full version of Access. The exact error
message states
"You do not have the necessary permissions to use the "\\Saturn\users\et
cetera\db1_backend.mdb" object. Have your system administrator or the person
who created this object establish the appropriate permissions for you."

 

[Matt]

I just tried converting the back end to an accdb also in an attempt to sans
user level security alltogether. Both the front end and the back end have
been converted to the 2k7 format, but it still asks for a login when I start
the database. When I package the database and deploy it to another PC in my
office, I still get an error message referencing the back_end.MDB file, not
the converted back_end.accdb file. I did update the references with the
linked table manager, so I'm at a loss at this point. Any help would be
greatly appreciated as I would love to get the package with runtime feature
working properly. Thanks in advance!

 

[Joan Wild]

I just tried converting the back end to an accdb also in an attempt to sans
user level security alltogether. Both the front end and the back end have
been converted to the 2k7 format, but it still asks for a login when I start
the database.

How are you starting it? Just a double-click? If so then your computer is joined by default to a secure mdw file. Use the workgroup administrator to rejoin system.mdw that ships with Access. (but this has nothing to do with your mdb)

When I package the database and deploy it to another PC in my
office, I still get an error message referencing the back_end.MDB file, not
the converted back_end.accdb file. I did update the references with the
linked table manager, so I'm at a loss at this point.

Check code that runs on startup, or code behind some startup form - there's a reference to the old backend somewhere.