solun
Programmer
- Apr 1, 1999
- 55
Access 2000 on Win2KPro
Backend lives on nice server, contains 23 tables with 3 to 600 records each (2100 kb).
Front end lives on individual users' machines. The front end has 20-odd queries, 20-odd forms and three reports. Granted, the forms are very complex with min. 3 subforms each.
For two days of every month, the users go out to field offices and communicate with the server via a 100mbsp (max) network connection.
Until recently opening one form took about a minute in the field. It now takes 20 in the field!!!! Compact & repair reduces the database size from 21,000 kb to 1,800 kb, but when the database is used again, it quickly shoots back up.
Ideas on how to diagnose this? fix it?
Thank you, oh great experts!
Backend lives on nice server, contains 23 tables with 3 to 600 records each (2100 kb).
Front end lives on individual users' machines. The front end has 20-odd queries, 20-odd forms and three reports. Granted, the forms are very complex with min. 3 subforms each.
For two days of every month, the users go out to field offices and communicate with the server via a 100mbsp (max) network connection.
Until recently opening one form took about a minute in the field. It now takes 20 in the field!!!! Compact & repair reduces the database size from 21,000 kb to 1,800 kb, but when the database is used again, it quickly shoots back up.
Ideas on how to diagnose this? fix it?
Thank you, oh great experts!