Managing Memory and Error 3048 in Access 2003
Posted on 2008-06-16
I have a very large applicaiton nearing completion. I have come into the problem that without to much difficulty users reach the memory limit of access. The error 3048 is sometimes thrown. Other times the program hangs.
How can I best manage for the limitations of access without causing the user to much greif. I would like to capture the out of memory error, send a warning message (msgbox-too many forms open, shut some) and shut down the form that was last open.
I have tried to do this by calling a custom error box function from the form and report error functions, but it doesn't always work properly. For example:
DispError "DMenuBar", "setReportMenu", Err.Number, Err.Description
It seems that the out of memory limits of access can be reached without an error being thrown. Is this the case? Any suggestions / discussion about the issue would be great.