Access 2007 access control is my showstopper :-(

Alvis

Learning is fun !
Local time
Today, 04:35
Joined
Feb 13, 2013
Messages
27
All -

How to really design access control your MS access application when you are rolling out to a larger group? This is much needed for the benefit of the users and to make sure that no one really changes the code or the design piece of the application.

The ACCDE option is not really working when the application is big. I have created around 15 forms and around 20 tables and I couldn't convert that to accde file ....

What options are available to really control access or atleast avoid users to change the design of the application ?

Please support and share tips and ideas ... one critical application I have developed for my team couldn't be rolled out just because of this constraint ... :-(

Thanks
Alvis Lazarus
 
Hello Alvis, sounds a bit strange, as in the application I have, am currently running for over 15 users and the content of the MS Access file is 64 Forms, 55 Queries and 33 (linked) tables.. and I give away ACCDE versions the size is not greater than 8 MB..
 
Try Debug > Compile first before trying to convert to ACCDE.
 
as the others have said - you cannot produce an accde if there are errors in your code - so you need to debug and remove errors - then you can make the accde.
 
Friends ... yup, I think that's the problem. My application is around 28MB now. I'll try to compile and then try the accde option ! Thanks !

Is there any other options available other than accde in 2007 ?
 
Well there is always Runtime.. Similar to ACCDE, does not allow changing code or deleting objects.. However if the user renames the ACCDR to ACCDB would simply be back to normal.. as in everything can be done.. So first ACCDE then to ACCDR is the right way to go about..

Information on Changing to Runtime - Resource by Microsoft.. Hope this helps..
 
Guyz ... it worked for me. Thanks a lot !
 

Users who are viewing this thread

Back
Top Bottom