Tim Bedborough
Registered User.
- Local time
- Today, 03:49
- Joined
- Nov 16, 2015
- Messages
- 42
Hi everyone.
Sorry for the ramble, hope it makes sense.
I'm using Access for data source back end tables as well as front end windows (objects - forms, reports etc). Back end and front end are split due to multi user front end requirements. All on on a local area network.
We had a minor scare today. Some of my form combo boxes were unable to show the options in the list. Not all.
I did a 'compact and repair' on the back end which fixed things. The old back end went from 116,000 KB to 20,000 KB. (I haven't done a C&R for a while).
I did a C&R on the front end but this dropped from 11300 KB to 11200 KB so didn't perceive this would have made much difference. The back end C&R was done first and fixed the issue in the front end on the larger file size before I did a C&R on the front end.
We are running 15 users approx although not all use the database or network at the same time so is probably limited to 6 or so at any 1 time. I have had feedback that this might be reaching the back end capacity of what Access can achieve in a multi user environment but we have run it this way on Access 2002 right up to 2015 when we moved over to Access 15 (or whatever it was in 2015) and then 365 and had a back end and front end rebuild. Moved from .mdb to .accdb.
So after all that the question is this. Does anyone consider these file sizes an issue with Access or the number of users? Reducing the back end by 1/5th approx fixed things but no idea if this was a file size issue or something else that the repair feature in Access identified and fixed.
We don't really want to have to move away from the current Access database set up but if file sizes will cause object functionality issues (e.g. combo drop lists), i'd rather be thinking about options before it breaks rather than when we get to capacity.
Any thoughts or tips much appreciated.
Thanks.
Sorry for the ramble, hope it makes sense.
I'm using Access for data source back end tables as well as front end windows (objects - forms, reports etc). Back end and front end are split due to multi user front end requirements. All on on a local area network.
We had a minor scare today. Some of my form combo boxes were unable to show the options in the list. Not all.
I did a 'compact and repair' on the back end which fixed things. The old back end went from 116,000 KB to 20,000 KB. (I haven't done a C&R for a while).
I did a C&R on the front end but this dropped from 11300 KB to 11200 KB so didn't perceive this would have made much difference. The back end C&R was done first and fixed the issue in the front end on the larger file size before I did a C&R on the front end.
We are running 15 users approx although not all use the database or network at the same time so is probably limited to 6 or so at any 1 time. I have had feedback that this might be reaching the back end capacity of what Access can achieve in a multi user environment but we have run it this way on Access 2002 right up to 2015 when we moved over to Access 15 (or whatever it was in 2015) and then 365 and had a back end and front end rebuild. Moved from .mdb to .accdb.
So after all that the question is this. Does anyone consider these file sizes an issue with Access or the number of users? Reducing the back end by 1/5th approx fixed things but no idea if this was a file size issue or something else that the repair feature in Access identified and fixed.
We don't really want to have to move away from the current Access database set up but if file sizes will cause object functionality issues (e.g. combo drop lists), i'd rather be thinking about options before it breaks rather than when we get to capacity.
Any thoughts or tips much appreciated.
Thanks.