Secure Database (2003) problem

Topic

New Reply

Hi,

I have a Secure Receipts database (Access 2003 – has been running perfectly since 1999) which I will need to run at a later date under Access 2007 – some of my current users were given new PC’s and instead of the full version of Access 2003 they were given Access 2007 run-time – this means that they cannot join the workgroup as needed. Is there an easy way around this? I understand from my own copy of Access 2007 on my laptop that User & Group Security can be used as long as the database is not converted to the new format. Yesterday, I copied the database to my laptop and re-created the User & Group permissions using the wizard and tested it out by logging on as different users and this worked great – however, when I copied everything back on to the network computer the database could only be used properly by someone with the full version of Access 2003 (after fixing the shortcut to point to the correct directories). Any assistance with this would be most appreciated.

Reply | Quote

Replies

You are right that a Secure Database can be used with 2007 provided it is not converted to 2007.

I have not tried this with the Runtime, but I expect it would work.
When you join a workgroup, Access applies the security settings to all databases. So it is very common to use the following strategy to open secured databases without joining the workgroup.

The strategy is this. Open the database with a shortcut with the following structure, which means “Open the database using permissions from the specified workgroup file”

“path to Access executable” “path to database” /WRKGRP “path to Workgroup Info file”
“C:Program Files (x86)Microsoft OfficeOffice12MSACCESS.EXE” “D:johnAccessHopscotchHopscotchSecure.mdb” /WRKGRP “D:johnAccessHopscotchHopscotch.mdw”

You can optionally add additional switches for /user “username” /pwd “password”

Reply | Quote

John,

I had already seen this structure when I needed to change the shortcut properties on the network computer, but still could not get it to work for other users, who had only the run-time version of Access 2007 on their PC’s. What I need is to somehow get this working on the run-time or else get the network people to put the full version on their PC’s.

Reply | Quote

When you say “the database could only be used properly”, exactly what happens to the others?

There could be another issue here. When you open any database with Access 2007 (including the full version) No Code is allowed to run, until you create a Trusted Location.
Until you do that, you see a warning that certain content has been disabled. Is this what is happening?

Reply | Quote

When you say “the database could only be used properly”, exactly what happens to the others?

They got an error message (can’t remember exactly what it said) and the database either would not load or loaded only the first time and not subsequently.

There could be another issue here. When you open any database with Access 2007 (including the full version) No Code is allowed to run, until you create a Trusted Location.

I will get our network people to look at this, as I believe that this sort of thing is restricted functionality.

Until you do that, you see a warning that certain content has been disabled. Is this what is happening?

I think I did see that message at some stage.

Reply | Quote