modle
asked on
A2010 program not releasing resources.
I have a 14MB .ADP application with a SQL Server 2005 backend. When run in A2010, the program (viewed in the task manager) opens in 47.6MB and grows by 20MB each time an "update contact information" screen is opened. The program size decreases about 1MB when the screen is closed (doing nothing but opening and closing the screen) but grows another ~20MB when that same screen is opened again. After 4 open/closes, the program size is 110MB and growing.
When I run exactly the same app with the same back end in A2003, the program grows a bit but only by ~2MB each time. Under A2003, the app starts at 36.5MB and after the same series of operations as above, it's size is 44.4MB. So it is growing a bit with each operation but much more slowly.
All the objects are released in the code that is being executed.
Has anyone run into this issue in A2010?
When I run exactly the same app with the same back end in A2003, the program grows a bit but only by ~2MB each time. Under A2003, the app starts at 36.5MB and after the same series of operations as above, it's size is 44.4MB. So it is growing a bit with each operation but much more slowly.
All the objects are released in the code that is being executed.
Has anyone run into this issue in A2010?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I will check with our IT about SP1. However, I believe I read what was "fixed" in SP1 and there was nothing about Access. Maybe I read the wrong document......
The solution has been.....that the user exits and reenters the app and continues. It's just a bit of a pain. PS: there are about 15 users at a time in this app. Only when someone is doing extensive data entry on multiple records (75K in the db all together) does the size creep interfere with usage.
Thanks for your help.
The solution has been.....that the user exits and reenters the app and continues. It's just a bit of a pain. PS: there are about 15 users at a time in this app. Only when someone is doing extensive data entry on multiple records (75K in the db all together) does the size creep interfere with usage.
Thanks for your help.
"Maybe I read the wrong document......"
I have seen docs showing what was fixed. However, certainly not a complete list.
mx
I have seen docs showing what was fixed. However, certainly not a complete list.
mx
<Only when someone is doing extensive data entry on multiple records (75K in the db all together)>
So you still may want to investigate ways to limit the updates, ...then perhaps the bloat might be "tolerable"?
Jeff
So you still may want to investigate ways to limit the updates, ...then perhaps the bloat might be "tolerable"?
Jeff
ASKER
I made sure Office 2010 SP1 was installed and tested again. No change - memory increases in 20MB chunks and never releases.
OK, sorry I could not help more...
ASKER
Are you suggesting C&R while it's running? I've never done that.....only done that on exit or in development.