I have this scenario:
At my place, Access is having performance issues, specifically when users are adding records through Forms. There are total of 14 tables and some of these tables have over 130k records with each one having a sub record (collapsables) which makes for a lot more.
There are various users adding new information to these tables and of course Access is having performance problems since these users access the same file through a shared folder over the network. By performance problems I mean that it takes 5-10 minutes to complete adding a record to the DB.
I was thinking that perhaps Splitting the DB would help, but I don't know if that is enough considering the huge amount of records stored in the file and the ones to come in the future.
Is there anything else besides DB splitting that should be taken into consideration?
I had one other crazy idea which was to export the tables onto another place (something like a copy for archival purposes) and then cut off the information 1 year from now and delete any data older than 1 year to lighten the burden Access is having, but this solution seems more likely prone to disaster.
Any help is appreciated!
At my place, Access is having performance issues, specifically when users are adding records through Forms. There are total of 14 tables and some of these tables have over 130k records with each one having a sub record (collapsables) which makes for a lot more.
There are various users adding new information to these tables and of course Access is having performance problems since these users access the same file through a shared folder over the network. By performance problems I mean that it takes 5-10 minutes to complete adding a record to the DB.
I was thinking that perhaps Splitting the DB would help, but I don't know if that is enough considering the huge amount of records stored in the file and the ones to come in the future.
Is there anything else besides DB splitting that should be taken into consideration?
I had one other crazy idea which was to export the tables onto another place (something like a copy for archival purposes) and then cut off the information 1 year from now and delete any data older than 1 year to lighten the burden Access is having, but this solution seems more likely prone to disaster.
Any help is appreciated!