You could always try a DISCONNECT/CONNECT; this will get rid of at least all the cursors and temporary tables. The only issue I see with using ZIP ROLLOUT within an application would be the long time it would take to restart the application. I remember having a utility in Windows 98 that restored memory unreleased by misbehaving programs; I don't know if something like that is available (or needed) for Windows XP and higher.
Javier, Javier Valencia, PE 913-829-0888 Office 913-915-3137 Cell 913-649-2904 Fax javier.valen...@vtgonline.com ________________________________________ From: rbase-l@rbase.com [mailto:rbas...@rbase.com] On Behalf Of karentel...@cs.com Sent: Tuesday, June 08, 2010 8:56 AM To: RBASE-L Mailing List Subject: [RBASE-L] - Re: Zip Rollout in windows? Javier: Oh, of course I realize that. I haven't used the ZIP command in years and years.... But don't you think it's interesting that the help screen says that when used in windows it helps to release memory? I've had times where strange things happen, like temp tables getting corrupted data, etc., where a restart of RBase always fixes things and I've wondered if there was a way to "reset" everything. I'm wondering now if I can use ZIP ROLLOUT to do that from within an app. Karen Karen, I believe that ZIP and ZIP ROLLOUT apply mostly to the DOS versions. ZIP has been replaced with LAUNCH and ZIP ROLLOUT was used in DOS when there was not enough memory to run R:Base and the external program. Javier,
