Forum Discussion
Access software size and users
Hi Matti,
Some questions about your system:
- What files does your Access application consist of?
- Is the application split into frontend and backend file?
- Does each user have his own frontend file?
- Which file exactly is inflating?
- Are there any error messages before Access crashes?
Servus
Karl
*********
http://AccessDevCon.com
https://www.donkarl.com
1. One file in server Access 2019 contains 10 tables
One file in workstations contains 200 queries, 100 forms, 30 reports , 120 macros
2. Backend in server and frontend in workstations
3. One frontend
4, File in server is inflating (maybe one of reports is doing this)
5. No error. Just slowing and stop system. New backup file is coming to server.
Matti
- isladogsOct 27, 2021MVP
I hope you mean one frontend for each user on their own workstation.
Are you using a persistent connection to the BE file? If not, I would recommend it
Does the frontend contain any tables e.g. 'temp' tables that are being written to on a regular basis?
Is Compact On close enabled in the FE? If so, disable it
One way you could test what happens before a crash is to test for available connections.
See Available Connections - Mendip Data Systems
If the number of available connections drops significantly, the FE will slow dramatically and then crash. If that is the cause, you can take remedial action to close objects when not in use
- Matti_HaapaniemiOct 28, 2021Copper Contributor
Each user has own frontend.
We have localnetwork 1 gb to server.
All tables are in server not frontend.
CompactOn Close disabled.
But available connections is intresting. we have lot of queries and reports and users
keep all open.
I try to test but error comes (form and report is copies9
- isladogsOct 28, 2021MVPThat sounds like a missing reference issue.
DAO is part of a standard reference library. For ACCDB files, you need the Microsoft Office xx.0 Access Database engine object library. For older MDB files, use the Microsoft DAO 3.6 Library.
Once that is installed the code should then run successfully.
You should soon notice why its a Good idea to close forms and reports when not in use as well as setting recorders to nothing when you finish using them.