The following is the setup of the Access Database I have created:
- Access 2010 Database with several tables and forms.
- The Database will be used by multiple users simultaneously
- The Database has been published to Office 365 (sharepoint) without being split.
- I create a separate 'user copy' which has the relevant tables/menus etc hidden to stop them accidentally deleting records. This means I have my own copy which has the tables and menus showing.
- Users will not be accessing the database from the web, but instead will have the 'user copy' installed on their local hard drive, and any data that is inputed by them feeds into the common database located on Office 365.
My questions are as follows:
1. Once the Database has been published to Office 365, and the 'user copies' distributed, I need the ability to amend both the tables (adding fields) and the forms, and distribute the new version of the 'user copies' to the relevant users. However, once the Database has been published, it does not seem to be possible to open the tables in Design View, only the forms. How do I amend the tables in Access on my computer?
2. Should I be splitting the Database (in the traditional back-end/front-end way) and only publishing the back-end tables to Access 365? If so, you end up with a rather confusing relationship scenario between the tables that you originally split, and then having to manually link the relevant forms to the new sharepoint tables.
3. I can't seem to get Record Locking working in any of these scenarios. I want users to be locked out from editing a record while someone else has a record open. I want them to be able to see it, but not edit it.
Any help much appreciated!
- Access 2010 Database with several tables and forms.
- The Database will be used by multiple users simultaneously
- The Database has been published to Office 365 (sharepoint) without being split.
- I create a separate 'user copy' which has the relevant tables/menus etc hidden to stop them accidentally deleting records. This means I have my own copy which has the tables and menus showing.
- Users will not be accessing the database from the web, but instead will have the 'user copy' installed on their local hard drive, and any data that is inputed by them feeds into the common database located on Office 365.
My questions are as follows:
1. Once the Database has been published to Office 365, and the 'user copies' distributed, I need the ability to amend both the tables (adding fields) and the forms, and distribute the new version of the 'user copies' to the relevant users. However, once the Database has been published, it does not seem to be possible to open the tables in Design View, only the forms. How do I amend the tables in Access on my computer?
2. Should I be splitting the Database (in the traditional back-end/front-end way) and only publishing the back-end tables to Access 365? If so, you end up with a rather confusing relationship scenario between the tables that you originally split, and then having to manually link the relevant forms to the new sharepoint tables.
3. I can't seem to get Record Locking working in any of these scenarios. I want users to be locked out from editing a record while someone else has a record open. I want them to be able to see it, but not edit it.
Any help much appreciated!
