To split or not to split?
- Thread starter AN60
- Start date
DavidWRouse
Registered User.
- Local time
- Today, 23:06
- Joined
- Jul 24, 2003
- Messages
- 42
If you are a single user then its not really worth it.
I have a DB with 5 people on a network, And i still have not split the DB it works fine, Each user has a Shortcut to the .mdb file.
I read that the benefits are:
1) Reduces network traffic when lots of users connected to one BD
2) The front end could be taken away and modified, and then updated on each persons computer when new front end had been completed. Thus minimal interuption of the users.
I have a DB with 5 people on a network, And i still have not split the DB it works fine, Each user has a Shortcut to the .mdb file.
I read that the benefits are:
1) Reduces network traffic when lots of users connected to one BD
2) The front end could be taken away and modified, and then updated on each persons computer when new front end had been completed. Thus minimal interuption of the users.
- Local time
- Today, 17:06
- Joined
- Feb 28, 2001
- Messages
- 30,558
There are other advantages to FE/BE split, but I have yet to take that plunge. On the other hand, for me it is coming soon.
1. FE/BE split means EACH DB can reach the maximum DB size separately (as opposed to a single DB with FE/BE co-resident). So if you have lots and lots of records, this MIGHT be helpful. But we are talking gigabyte files for the limit in question.
2. FE/BE split means easier migration of the BE to another platform besided Access in the future. Like ORACLE, SQLServer, or other PC/DB software.
3. Mixed versions of Access FE can use the same BE up to a point.
4. For your savvy users, allowing them to have private copies of the FE allows them to have their own little personal queries that are useful to them but to no-one else. If they are savvy enough to make their own queries, they should also be savvy enough to export their queries to SQL if they need to get an updated copy of the FE, then re-import their home-grown stuff to the new FE. This allows you to de-clutter your FE.
1. FE/BE split means EACH DB can reach the maximum DB size separately (as opposed to a single DB with FE/BE co-resident). So if you have lots and lots of records, this MIGHT be helpful. But we are talking gigabyte files for the limit in question.
2. FE/BE split means easier migration of the BE to another platform besided Access in the future. Like ORACLE, SQLServer, or other PC/DB software.
3. Mixed versions of Access FE can use the same BE up to a point.
4. For your savvy users, allowing them to have private copies of the FE allows them to have their own little personal queries that are useful to them but to no-one else. If they are savvy enough to make their own queries, they should also be savvy enough to export their queries to SQL if they need to get an updated copy of the FE, then re-import their home-grown stuff to the new FE. This allows you to de-clutter your FE.
He is saying that multiple versions of access can use the same back end data.
So if some people have 97 and some people have 2k, having it NOT split, means it can cause troubles for either.
Having a split, you can have a version for 97, and a version for 2k.
So if some people have 97 and some people have 2k, having it NOT split, means it can cause troubles for either.
Having a split, you can have a version for 97, and a version for 2k.
Similar threads
