Mike, Apparently there are more than one kind of shortcut.
The only way I have found to create the shortcut with the memory settings is to browse for the target and point it to rbase65.exe Then you can modify the shortcut to run a batch file. In any case, I have found that I get the same results regardless of whether I use the forced shortcut as just described or use the standard shortcut which is produced without all the hacking. The only way I have found to trigger off the offending memory leak is to use ZIP RETURN whatevercommand somewhere in the code. >From that point on, until I exit RBase for DOS, any database access leaks memory. If there are any other commands that trigger this behaviour, I have not discovered them. Anyone who has a hint of what other commands also could trigger this condition, just use them instead of my ZIP RETURN in your tests. The more complete info we get to Mike the better. Here is the code I used to replicate the memory leaks: DISC SET MULTI ON set escape on conn concomp -- ANY USE OF ZIP RETURN -- WILL CAUSE RBASE TO START EATING MEMORY -- AS COMMANDS ARE EXECUTED -- TO MAKE SURE THIS TEST WILL WORK FOR YOU -- SAY: ZIP RETURN COMMAND.COM -- AT THE R> -- IF YOU GET A DOS WINDOW, THAT IS COOL, TYPE EXIT TO RETURN TO RBASE -- THIS COMMAND USES THE /C PARAMETER -- TO TELL COMMAND.COM TO COME BACK IMMEDIATELY ZIP RETURN COMMAND.COM /C label loop select count(*) from customer goto loop return Happy Memory Leak Hunting Dennis McGrath
