bobsan42
Well-known Member
- Joined
- Jul 14, 2010
- Messages
- 1,946
- Office Version
- 365
- 2019
- 2016
- 2013
- Platform
- Windows
Hello guys,
I am currently developing a small database.
I need advice on several points and possibly code (if readily available) - I wouldn't want to invest too much time in this.
1. I need a bundle of code to force the user to take the the easiest way - to force him/her to use the provided menu (instead of starting to enter in tables, forms, etc. w/o control). It does not need to be highly secure, password protected etc. - just maybe hide as many of the interface elements like ribbon and the search bar (in Navigation Pane), prevent changes to the Navigation Pane for example - if more is necessary I can't think of it at the moment.
2. I intend to use the navigation pane as main interface and menu. Is this a good idea or a bad one?
3. Is there a way a database file to be opened as read-only? How good is the /ro command line switch?
To explain the situation (I have a lot of worries about this approach but it is not my choice):
The guy is using google drive to share the db file and to make it available to several people. So someone will open it from the local Google drive folder, work in it, then close it. Then Google drive will sync it. Then someone else will open it, look at some data and close it. Apart from the data possibly being incomplete, the mess can become total IMO. You cannot control which file will be synced last.
Any ideas?
I am currently developing a small database.
I need advice on several points and possibly code (if readily available) - I wouldn't want to invest too much time in this.
1. I need a bundle of code to force the user to take the the easiest way - to force him/her to use the provided menu (instead of starting to enter in tables, forms, etc. w/o control). It does not need to be highly secure, password protected etc. - just maybe hide as many of the interface elements like ribbon and the search bar (in Navigation Pane), prevent changes to the Navigation Pane for example - if more is necessary I can't think of it at the moment.
2. I intend to use the navigation pane as main interface and menu. Is this a good idea or a bad one?
3. Is there a way a database file to be opened as read-only? How good is the /ro command line switch?
To explain the situation (I have a lot of worries about this approach but it is not my choice):
The guy is using google drive to share the db file and to make it available to several people. So someone will open it from the local Google drive folder, work in it, then close it. Then Google drive will sync it. Then someone else will open it, look at some data and close it. Apart from the data possibly being incomplete, the mess can become total IMO. You cannot control which file will be synced last.
Any ideas?