MonsterMike
New member
- Local time
- Today, 01:32
- Joined
- Aug 9, 2012
- Messages
- 6
Hello,
This is my first post here so apologies if I violate any norms...
My question:
Which is better for multi-users: Splitting Database OR Linking to Data Source?
I understand splitting the database into front-end and back-end could be the best way to allow multiple users to interact with the database. But what about the option of creating multiple databases that link together? Is it similar since the splitting option actually links the front-end to the back-end?
Supposing I had 20 users, my understanding is that the option to "Link to the data source by creating a linked table" would mean I would have to have 20 different database files that all link together and would be updated instantly as any field changes are made.
However, using the splitting method, I would create one front-end file and distribute to all 20 users, and they would all link to the back-end database.
So which method is better?
Any input or suggestions are greatly appreciated.
Thank you,
Mike
This is my first post here so apologies if I violate any norms...
My question:
Which is better for multi-users: Splitting Database OR Linking to Data Source?
I understand splitting the database into front-end and back-end could be the best way to allow multiple users to interact with the database. But what about the option of creating multiple databases that link together? Is it similar since the splitting option actually links the front-end to the back-end?
Supposing I had 20 users, my understanding is that the option to "Link to the data source by creating a linked table" would mean I would have to have 20 different database files that all link together and would be updated instantly as any field changes are made.
However, using the splitting method, I would create one front-end file and distribute to all 20 users, and they would all link to the back-end database.
So which method is better?
Any input or suggestions are greatly appreciated.
Thank you,
Mike