Out of Memory error in 64bit Access 2010
I am running Windows 7 64bit and Office 2010 64bit. i have an Access application that when opened, displays an error that i have to add ptrsafe to some declarations. I ran through and added this to every area of code that came up as needing this. Now when i open the database, i immediately get an Out of Memory error. I have tried decompiling, compacting and compiling. nothing gets rid of this. anyone know how to resolve this?
thanks!
thanks!
ASKER
its like 24mb.the problem only occurs in the 64bit. workstation. as an update i installed SP1 of office 2010 and i got farther in that the database opened and compiled with the error but the minute i tried to attach to an mde i use to run reports, it gave me the out of memory error again and seems to have toasted the whole database now. grrr.....
How much RAM do you have in the system?
Also verify your paging has not been changes...
(Just covering the basics)
Also verify your paging has not been changes...
(Just covering the basics)
Have you done a Compact and Repair?
Also 23 MB is include all your tables and reference databases?
Also 23 MB is include all your tables and reference databases?
Have you checked the References on the 64-bit machine? To do that, open your database, open the VBA Editor and click Tools - References. Are any marked as MISSING? If so, you'll have to resolve that before proceeding. If you'd list the References you have, we can review them and perhaps give advice.
Are you using ANY ActiveX controls in the database (like a Calendar control, for example)? If so, then you'll have to remove that if you stay with the 64-bit Office versions (or upgrade to the 64-bit version of the control, and there are very, very few of those currently available).
What's the reason for using the 64-bit version of Office? Most developers (and Microsoft) recommend using the 32-bit versions unless you have a definite need for features in the 64-bit versions. Apps developed on the 64-bit platform can ONLY be used by others running the 64-bit version of Office.
Are you using ANY ActiveX controls in the database (like a Calendar control, for example)? If so, then you'll have to remove that if you stay with the 64-bit Office versions (or upgrade to the 64-bit version of the control, and there are very, very few of those currently available).
What's the reason for using the 64-bit version of Office? Most developers (and Microsoft) recommend using the 32-bit versions unless you have a definite need for features in the 64-bit versions. Apps developed on the 64-bit platform can ONLY be used by others running the 64-bit version of Office.
ASKER
I have 4GB RAM. the front end is about 24-43mb and there are 2 backend databases. I am using samples for now and they are only aboutr 10mb apiece. I connect to an mde database as well to run reports. this database is about 14mb.
I do use comctl32.ocx which I am beginning to suspect may be all or at least part of the problem.
I do not prefer to use 64bit but have 2 clients so far that have decided to go 64bit and now are having problems running my application. I would prefer to deal only with 32bit but i am trying to find a solution that will allow them to run my 32 bit application on their 64bit systems. thank you!!
I do use comctl32.ocx which I am beginning to suspect may be all or at least part of the problem.
I do not prefer to use 64bit but have 2 clients so far that have decided to go 64bit and now are having problems running my application. I would prefer to deal only with 32bit but i am trying to find a solution that will allow them to run my 32 bit application on their 64bit systems. thank you!!
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
thanks for the info. That confirms what I have been reading as well. Do you know if there is a way to have it run in something like a windows xp or 32 bit compatibility mode? Or does microsoft have an alternate control that can be used for treeview? Just looking for work arounds. I use comctrl32.ocx for the treeview for creating an inventory assembly tree.
I think the limit is like 2 GB.