hi Ozair,
maybe there are places in your code that you're not releasing objects, and that is keeping those connections "alive" unnecessarily. As a general rule, at the end of each procedure, I add code to release object variables for that procedure
Daniel has a helpful article. He calls this sort of thing "self-healing-object-variables"
https://www.devhut.net/self-healing-object-variables
kind regards,
crystal
Hi,
I need experts advice on how big to too BIG for a single MS Access file?
We are struggling with a nasty "Out Of Memory" bug that stops us far too frequently.
As soon as it appears, it undoes the most recent written code - eventually failing to compile the file.
What I already have tried (temporarily solves the problem)
=============================================
- Compact & Repair
- Creating a brand new ACCDB then exporting all objects to it.
- Decompile
Maybe we have a really large MS Access application that consists of
1452 Forms
1500 MS Access saved queries
750 Tables (MS SQL 2012)
450 Reports
Other Information
==============
We use RDP to connect to the Server.
Windows Server 2012 R2 on Xeon CPU with 154GB RAM
MS Office 2016 (64-bit)
Any help is greatly appreciated.
Best,
Ozair
Tidak ada komentar:
Posting Komentar