Front end data minupilation

[goosegoose35]

Hello, I have a data base where we have 4 users using a front end and the back end stored on a network drive. I have forms set up so no data can be edited once entered and our idea was to have a dedicated person who could access the back end if we needed to fix any errors to ensure data integrity.

Here is the issue. any user can access the table that is storing the data via the linked table. other than hiding the table, is there a way to prevent data being changed from the front end? Thanks.

[Toyman]

Hello, I have a data base where we have 4 users using a front end and the back end stored on a network drive. I have forms set up so no data can be edited once entered and our idea was to have a dedicated person who could access the back end if we needed to fix any errors to ensure data integrity.

Here is the issue. any user can access the table that is storing the data via the linked table. other than hiding the table, is there a way to prevent data being changed from the front end? Thanks.

Set the start up property of the database to open up a switchboard form (menus) and hide the db window and disable the AllowByPassKey

[goosegoose35]

Hi, thanks for the response, I am not very familiar on how to set up switchboards and what not. I have found a work around for now where i hid the table and gave them a snapshot query so they can see the table view and not edit anything. They have less knowledge than I do for access (the 4 users) so this will work for now.

how would I implement your solution? Thanks.

[Toyman]

Hi, thanks for the response, I am not very familiar on how to set up switchboards and what not. I have found a work around for now where i hid the table and gave them a snapshot query so they can see the table view and not edit anything. They have less knowledge than I do for access (the 4 users) so this will work for now.

how would I implement your solution? Thanks.

First do not let your user have direct access to tables and queries. You don't have any control on what they do with the records. Always let your users access the db records via forms or report. In forms and reports, you can set the properties to restrict how the records are accessed. With that said. A switchboard is nothing more than a form containing buttons or other db object you set to navagate to other forms or report which your users can access. Access provides a switchboard wizzard to help you create a basic switchboard or you can create one with codes or macros.

As stated earlier, do not let your user access the records directly from tables or queries. Instead, create forms and reports for their use. For example, lets say I have a table containing Personnel Information, and I want the user to access Personnel information. I would create a form bound to a query of the Personnel table. In this form, I can lock the fields so that the users cannot change the data or I can unlock the fields to allow certain people the ability to change the data; I have control over the use of the data in a form and not in a table.

Once you set up your Personnel form, you simply create a command button in the switchboard form which will open the Personnel form. In the main options setting of the db window, select "Current Database". In this window, you can set it so that the Switchboard form is the form to open once the database is access. In the same window, you can set other setting such as hiding the db window to prevent user from access the db objects. Finally, before you deploy your db, disable the AllowByPassKey setting. This will prevent your user from using the Shift+Open to access the db window. Search the phrase, "AllowByPassKey" in the forum or google and you will find directions on how to disable this. Good luck....

[goosegoose35]

First do not let your user have direct access to tables and queries. You don't have any control on what they do with the records. Always let your users access the db records via forms or report. In forms and reports, you can set the properties to restrict how the records are accessed. With that said. A switchboard is nothing more than a form containing buttons or other db object you set to navagate to other forms or report which your users can access. Access provides a switchboard wizzard to help you create a basic switchboard or you can create one with codes or macros.

As stated earlier, do not let your user access the records directly from tables or queries. Instead, create forms and reports for their use. For example, lets say I have a table containing Personnel Information, and I want the user to access Personnel information. I would create a form bound to a query of the Personnel table. In this form, I can lock the fields so that the users cannot change the data or I can unlock the fields to allow certain people the ability to change the data; I have control over the use of the data in a form and not in a table.

Once you set up your Personnel form, you simply create a command button in the switchboard form which will open the Personnel form. In the main options setting of the db window, select "Current Database". In this window, you can set it so that the Switchboard form is the form to open once the database is access. In the same window, you can set other setting such as hiding the db window to prevent user from access the db objects. Finally, before you deploy your db, disable the AllowByPassKey setting. This will prevent your user from using the Shift+Open to access the db window. Search the phrase, "AllowByPassKey" in the forum or google and you will find directions on how to disable this. Good luck....

This is what I am trying to do, however the front end is linked to the table in the back end, and you can open the linked table in the front end still. I have it hidden for now and the other users have no idea about access, but for the future we need to get this cracking. The thing is we need these people to input data, and once it is entered, not be able to change it except for a few fields. Any changes are going to be made by a database admin in case of misskeying or other errors. Thanks for your help on this.

[Toyman]

This is what I am trying to do, however the front end is linked to the table in the back end, and you can open the linked table in the front end still. I have it hidden for now and the other users have no idea about access, but for the future we need to get this cracking. The thing is we need these people to input data, and once it is entered, not be able to change it except for a few fields. Any changes are going to be made by a database admin in case of misskeying or other errors. Thanks for your help on this.

Make sure you do this:
"before you deploy your db, disable the AllowByPassKey setting. This will prevent your user from using the Shift+Open to access the db window. Search the phrase, "AllowByPassKey" in the forum or google and you will find directions on how to disable this. "

[boblarson]

Also, not only setting the AllowBypassKey setting, you need to go to the Startup Options and uncheck the USE ACCESS SPECIAL KEYS checkbox so they can't hit F11 to show the Navigation Pane window (and also make sure to uncheck the SHOW NAVIGATION PANE checkbox as well).

[goosegoose35]

Also, not only setting the AllowBypassKey setting, you need to go to the Startup Options and uncheck the USE ACCESS SPECIAL KEYS checkbox so they can't hit F11 to show the Navigation Pane window (and also make sure to uncheck the SHOW NAVIGATION PANE checkbox as well).

Thanks a lot, here is another question, can't they just go into the access options and tick the box back to get to the navigation pane? Is there a way to disable that all together? thanks.