on an (ir)regular basis, we can't save a(ny) file (doc, xls,...) because the network drive is out of memory. Then we have to save our file to our local disk and wait (or do efforts) untill there's enough free memory again.
Now I wonder if this might be one of the causes of corruption issues with our shared database... and I would like to take some preventive measures.
One method I could think of is
(i) set a minimum under which Access can't function properly;
(ii) check free memory space (*) and intervene at crucial situations.
In our set up (front-end mde + back-end mdb), I guess these stages could be when users:
- open database: mention free memory at main menu label or message box;
- edit or add data (BeforeUpdate event): inform user of memory status, cancel add/edit and ask to try again later.
- as a safe minimum, I would take e.g. 10MB... knowing that remaining disk space can get filled pretty fast. The drive is shared with many hundreds of users... and when the server is getting full, it's often because of a member uploading pictures or whatever large (number of) file(s);
- this procedure is to be used along with regular compact & repair (as far as possible) and backup;
- renewal or upgrade of servers is not an issue. Upgrade to informix back-end on another server might be... but may drag on for another couple or months or year...
Any comments or suggestions?
(*) I'll probably use the API GetDiskFreeSpaceEx function on the back end's drive.