-
If you would like to post, please check out the MrExcel Message Board FAQ and register here. If you forgot your password, you can reset your password.
Mutliuser accessing DB
- Thread starter Ragnar78
- Start date
Thx for the reply...
I was asking this cause, i'm creating a database that will be used as a history tool by users...so each user can use this DB to enter data.
Now this DB is on a shred folder and people might be editing it together...
I was wondering if this is possible...and if the refreshing is essential (probably other than .requery)
Thx again
I was asking this cause, i'm creating a database that will be used as a history tool by users...so each user can use this DB to enter data.
Now this DB is on a shred folder and people might be editing it together...
I was wondering if this is possible...and if the refreshing is essential (probably other than .requery)
Thx again
Upvote
0
Me again
This is where the ADO cursor types come in. Access supports 4 ADO cursor types. Each one has a specific action that affects your systems resources.
The cursors are Foreward-Only, Static, Keyset and Dynamic. Foreward-Only is the simplist of all, but will only allow you to read the recodset one way and will not show any changes to the database by oher users. Static shows a copy of a set of records when the recordset was created but will not show any changes made to that set. Keyset shows all records at the time the connection is made but will show no new records. Dynamic will show all new records and removes all deleted records.
Dynamic is the most comprehensive choice but you will feel the hit your sstem takes as it continually makes changes to the recordset. Keyset will show new data added by other users, but will lock you out of deleted records.
If you wish to see data changes "on the fly" so-to-speak then the keyset cursor is for you. If you don't need to know what other people are doing then a Static cursor is fine. If you wish to see any and all changes as they happen then a Dynamic cursor is what you require.
Just be advised that if your dataset is large and you choose a client-side (the recordeset resides in your systems memory) cursor then you must choose a Static cursor, but if you choose a server-side ciursor then you can choose any of the four.
The Access help has a lot of information on cursors.
anvil19
This is where the ADO cursor types come in. Access supports 4 ADO cursor types. Each one has a specific action that affects your systems resources.
The cursors are Foreward-Only, Static, Keyset and Dynamic. Foreward-Only is the simplist of all, but will only allow you to read the recodset one way and will not show any changes to the database by oher users. Static shows a copy of a set of records when the recordset was created but will not show any changes made to that set. Keyset shows all records at the time the connection is made but will show no new records. Dynamic will show all new records and removes all deleted records.
Dynamic is the most comprehensive choice but you will feel the hit your sstem takes as it continually makes changes to the recordset. Keyset will show new data added by other users, but will lock you out of deleted records.
If you wish to see data changes "on the fly" so-to-speak then the keyset cursor is for you. If you don't need to know what other people are doing then a Static cursor is fine. If you wish to see any and all changes as they happen then a Dynamic cursor is what you require.
Just be advised that if your dataset is large and you choose a client-side (the recordeset resides in your systems memory) cursor then you must choose a Static cursor, but if you choose a server-side ciursor then you can choose any of the four.
The Access help has a lot of information on cursors.
anvil19
Upvote
0
SydneyGeek
MrExcel MVP
- Joined
- Aug 5, 2003
- Messages
- 12,251
To add to Anvil's comments, the typical way to set this up is to split the database. The backend will contain the data tables and live in the shared folder. The front end will contain everything else, and each user will have a copy on their machine or private drive. This way, multiple users can view and edit the data at once. Also, if you change any queries, forms or reports, you just distribute the new front end to the users and the data is left untouched.
As an additional precaution to stop users messing up the logic of queries, forms etc, the front-end can be saved as an MDE file which still allows users to log in and run any queries / forms / reports, BUT : they cannot change any code, queries, forms, report layouts. Macros are NOT protected, however.
Denis
As an additional precaution to stop users messing up the logic of queries, forms etc, the front-end can be saved as an MDE file which still allows users to log in and run any queries / forms / reports, BUT : they cannot change any code, queries, forms, report layouts. Macros are NOT protected, however.
Denis
Upvote
0
Similar threads
- Question
