Dev Edition Compiled DB with a Security Worgroup file

[Jasontm01]

I have an Access Database compiled with Developer Edition so the users can run it without having Access installed.
This database has a login for each user via the workgroup file.
This database uses a backend database file for the actual data, the "interface" part of the DB is what is compiled and has the workgroup file.

Not sure how much the above matters.. but here is what I want to do. I want to be able to add/change/remove user accounts for login to the database without having to recompile it. Is this possible? If so, how would I do it?

I do not plan to personally oversee the admin of this DB forever so I really need to be able to have the new admin person take over add/remove of accounts without having to use Developer Edition to recompile.

 

[Pat Hartman]

I have an Access Database compiled with Developer Edition

- creating a distribution package with the packaging wizard did not do ANYTHING to your db except compress it into a file that the installation wizard could expand. Cab files are the installation wizard's version of zip files.

This database uses a backend database file for the actual data, the "interface" part of the DB is what is compiled and has the workgroup file.

- If the db has been converted to an .mde, all the source code has been removed and only the tokenized code remains. This is not technically complied. Compiling a program results in an .exe or .dll or some other executable file type. An .mde is not an executable file and it can be made by ANY version of Access EXCEPT the Runtime version and has NOTHING to do with the Developer Edition.

Once a person has the Access runtime installed, you can just send them replacement .mdb or .mde files along with the modified workgroup file.

For new installations, you need to create a new package with the updated db and workgroup files.

 

[Jasontm01]

Well I dont think it made an MDE, and "compiled" definitely isnt the right term.. but basically these people will not have access to the Developer Edition once I hand over full support to them.

They would like to be able to add new users to the database from time to time. Is there a way they can generate a new security workgroup file without having the Developer Edition?

The way I have it work right now.. The users install the application, it runs without having MS Access installed on the PC. The shortcut links to a LOCAL MBD file and to a Network share for the Backend file and the Workgroup file. What Im wondering is can I have someone just generate an updates workgroup file and replace the one on that network share with the updated one using a standard version of MS Access?? (or would that break the whole thing since it wasnt redone through the Developer Edition)

 

[Pat Hartman]

Well I dont think it made an MDE

- IT doesn't make .mde's. YOU make .mde's. All IT does is create installation packages.

The users install the application, it runs without having MS Access installed on the PC

- The users certainly do have Access installed! Your installation package INSTALLED the Runtime version of MSAccess, that's what's running the db.

You need at least one user with admin permission. That user should be able to add new users. Whoever is going to be assigned this permission will probably need the regular retail version of Access (they don't need Office Developer installed). I don't think you can get to the security stuff if you are using the Runtime to run the db because you don't have access to the full menus. You could add your own form to let them do this from within the application.

or would that break the whole thing since it wasnt redone through the Developer Edition

- You need to read the documentation. You are very confused about what the Package and Deployement wizard is doing.