Salut, JM
1. We use it strictly in the DOS environment. The same db on the same network on the
same PC does not display memory leaks when running RBWin.
2. ZIP RETURN does not close the db, does not clear the variables. It just hibernates
RBase for a couple of seconds.
3. We added a message at the top of the screen that says RESTARTING R:BASE
so the user knows what is going on.
4. As WXP uses the same pseudo-DOS environment, I do not see where it would be
different, but I have not personally tested it.
"J.M. GRATIAS" <[EMAIL PROTECTED]> wrote:
>
>>>
>Mike, we use ZIP RETURN to do this. Make sure that you use the full Command
>/c. We don't bother with the command file, we just pass the EXIT to the
>routine. Works on W2K machines.
>SET VAR vCommand = +
> �('ZIP RETURN' & (ENVVAL('COMSPEC')) & '/C EXIT')
>&vCommand
><<
>
>I have some questions about this tip :
>
>1) Does this works (release memory) only with RBDOS, or also with RBW6.5++
>?
>2) I suppose that the DB have to be closed and reopenned after ZIP ?
>3) Is it possible to avoid or hide the flashing black screen at ZIP time ?
>4) Is this supposed to work also with WXP ?
>
>TIA
>
>J.M. GRATIAS, Logimatique
>
>
--
Albert Berry
Full Time Consultant to
PSD Solutions
350 West Hubbard, Suite 210
Chicago, IL 60610
312-828-9253 Ext. 32
__________________________________________________________________
The NEW Netscape 7.0 browser is now available. Upgrade now!
http://channels.netscape.com/ns/browsers/download.jsp
Get your own FREE, personal Netscape Mail account today at http://webmail.netscape.com/
