Application Distribution

[clauses]

I have created an access application for use around the office. Everyone currently has a licensed copy of Office XP on their PC and I would like to place my application on the server so that all users can use the application. I does not appear that the deployment wizard is available with XP, and since we utilize the campus agreement I cant really oder a copy of offfice developer so I am not real sure how to proceed. I have placed the front and backend databases on the server and am able to acces them from my PC but every time I open the front end database I still see the database window and am able to make changes to the databases. Using the startup from the toolbar I have made sure the box used to display the database window was not checked but it still shows up.

 

[ElsVanMiert]

You have a security problem

I strongly suggest that you change the architecture of your application:
The frontend has to be a MDE in order to protect everything except the tables and macros.
Install one copy of the FE on each client.
If you want to more security, you have to read the MS white paper on Security and the security-related articles in the ACCESS Online Encyclopedia at www.unsoftwareag.com .
Be sure to have understood the securizing procedure thoroughly, otherwise you will get into big problems!

 

[Pat Hartman]

The Developer's edition isn't going to do anything for you. It DOES NOT IN ANY WAY change your db. It simply gives you a license to install the runtime version of MSAccess.exe on multiple PCs. Since your users already have the retail version of MSAccess.exe installed, take Els' suggestions to increase your db's security.

While it is true, that you cannot get into design view of any db by opening it with the runtime version, there is noting to stop people from opening your db with their retail version. That's why making an .mde and adding some security is necessary if you don't want the users sinffing around behind the scenes and changing things.