Microsoft Access Database (Access XP) 1

[rrobinsonmis]

I have created a tracking database and have set it up as an application using different forms to access the data in the database. How can I prevent the user from getting to the tables, forms, and reports but use the database just to enter and edit data? I will have to access the tables, forms, and reports to make any updates to the structure of the database.

Thanks.

 

[chris153]

Hi,

There are several options available to you assuming that your database:

Change the start-up options: You can change the stat-up options so that the database window is not available to the user. Unfortunately, if the user holds the shift key down when entering the database this action will be cancelled. You could uncheck the hidden objects box (tools, options, view) and hide each database object by right clicking on the object in the database window and going into its properties.

Create an MDE: If you turn the front end of your database into an MDE the user won't be able to make any design changes. However, they'll still be able to open the database objects and therefore alter data directly through the tables.

Create a run-time version: This is the most secure method because the database window cannot be viewed. This also has the added advantage that the user doesn't need to have Microsoft Access installed on there PC if you distribute the whole run-time package.

The problem with creating a run-time version or an MDE is that when you make any design changes to the front-end of the database you will need to re-distribute it.

Hope this helps!

 

[chris153]

Hi,

There are several options available to you:

Change the start-up options: You can change the stat-up options so that the database window is not available to the user. Unfortunately, if the user holds the shift key down when entering the database this action will be cancelled. You could uncheck the hidden objects box (tools, options, view) and hide each database object by right clicking on the object in the database window and going into its properties.

Create an MDE: If you turn the front end of your database into an MDE the user won't be able to make any design changes. However, they'll still be able to open the database objects and therefore alter data directly through the tables.

Create a run-time version: This is the most secure method because the database window cannot be viewed. This also has the added advantage that the user doesn't need to have Microsoft Access installed on there PC if you distribute the whole run-time package.

The problem with creating a run-time version or an MDE is that when you make any design changes to the front-end of the database you will need to re-distribute it.

Hope this helps!

 

[OhioSteve]

As Chris said, you can change the startup options so that the database window doesn't appear. In addition, it is really easy to eliminate the default toolbar and menubar. I usually replace them with a blank toolbar and menubar.


Compiling the app or creating an .mde is certainly possible, but it is alot of work.

 

[rrobinsonmis]

Thank You for your responses. I want to use the runtime option. Is the only way to get the Packaging Wizard Add-In is through Office XP Developer? It is not listed in my add-in list.

 

[OhioSteve]

Its been a long time since I compiled something in Access. But I do seem to remember that you needed an add-in to compile. However, I don't recall it costing extra.