> Ref. #1585, #2382, #4430; note implicit conversions toVariant should be ignored, to avoid flagging arguments to the many built-in functions that take Variant parameters.
BLARGH! I am getting a persistant "Out of memory" message any time I try to edit any code in this VBA project. No code is running when I get the error. It's the VBE throwing the error when I try to edit a line. I have uninstalled RD and all addins. The host is 64-bit MSAccess.
Has anyone been so fortunate to see such a problem?
Access is using 440MB of RAM and I am decidedly not out of memory by any measure.
I have run MSACCESS.EXE /decompile against the file
I did another de-compile but this time I changed the code (adding a comment) before hitting compile again. Then I did C&R. Size went down to 4MB. It was letting me edit for a second but now the OOM error is back... I hate Access
@HackSlash Sorry missed that. It is a pretty small file so don't see how OOM would factor in. The only thought is that if there's a runaway code making objects that you weren't expecting to create, it might OOM. 440 MB is pretty high for plain Access (IME, it usually runs ~20 MB vanilla)
VBA Rubberducking
VBA Rubberducking