hiya, just wondering if this is a documented bug or not. i'm doing some auto-generated web pages which require bucketloads of map images saved as PNG, so using integrated mapping through MS Access i issue a command such as:
############## Save window 666 as "c:\MapImage.PNG" Type "PNG" ############## after doing a bunch of these (say 30 per page, and having done about 10 pages) i noticed my pooter was really chugging along. i checked task manager, and the MAPINFOW.EXE process was using 140MB of memory. i have repeated this process under several circumstances, and i can confirm that every time i use the SAVE WINDOW AS command for just a small map image in PNG format, MAPINFOW.EXE scavenges between 700k-1MB of RAM and doesn't release it back to the system. i'm using MI Pro V7.0, Release Build 22. as i intend on using this feature quite heavily in the near future, i'm wondering if anyone has resolved this issue in any way. i don't want to have my program have to close and re-open mapinfo every 5 minutes to give resources back. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ashley simmonds disclaimer: the views expressed in this email may be a health hazard ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ --------------------------------------------------------------------- List hosting provided by Directions Magazine | www.directionsmag.com | To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Message number: 10344
