S
Shane Suebsahakarn
Hi all,
This might be one of those things for which there is no workaround. I'm
using A2K2, and using it to perform a very large batch ouput. Both the front
and back ends are MDB files, so no SQL Server involved here. Both SP3 and Jet
SP8 have been updated, and the platform is running on a dual-processor 3Ghz
Xeon Win2K3 Server box with 2GB RAM.
The batch run outputs 6 or 7 reports to approximately 16-17,000 snapshot
files None of the reports is particularly complex except for one which
contains 13 subreports, placed in the group headers and footers and are
dynamically hidden based on the contents of a recordset, and two chart
objects. Only one of the reports has a graphic on it (a linked bmp, held in
an image control). During the loop, several recordsets are initialised and
closed (properly set to Nothing).
After approximately 10,000 or so items, I get a "There isn't enough memory
to perform this operation. Close any needed programs...etc.". The only way to
get the operation to continue is to quit Access and restart from the failed
point. Task Manager shows about 65MB in use by msaccess.exe and large amounts
reported as free.
I have looked at a couple of post-SP3 hotfixes, but they don't seem to apply
to this situation as I'm not switching any items between datasheet and design
view or using SQL Server.
If anyone could shed any light on this or suggest a fix/workaround, I'd be
very grateful.
Shane.
This might be one of those things for which there is no workaround. I'm
using A2K2, and using it to perform a very large batch ouput. Both the front
and back ends are MDB files, so no SQL Server involved here. Both SP3 and Jet
SP8 have been updated, and the platform is running on a dual-processor 3Ghz
Xeon Win2K3 Server box with 2GB RAM.
The batch run outputs 6 or 7 reports to approximately 16-17,000 snapshot
files None of the reports is particularly complex except for one which
contains 13 subreports, placed in the group headers and footers and are
dynamically hidden based on the contents of a recordset, and two chart
objects. Only one of the reports has a graphic on it (a linked bmp, held in
an image control). During the loop, several recordsets are initialised and
closed (properly set to Nothing).
After approximately 10,000 or so items, I get a "There isn't enough memory
to perform this operation. Close any needed programs...etc.". The only way to
get the operation to continue is to quit Access and restart from the failed
point. Task Manager shows about 65MB in use by msaccess.exe and large amounts
reported as free.
I have looked at a couple of post-SP3 hotfixes, but they don't seem to apply
to this situation as I'm not switching any items between datasheet and design
view or using SQL Server.
If anyone could shed any light on this or suggest a fix/workaround, I'd be
very grateful.
Shane.