>Hi Valeria,
>
>Thanks for your tip. I have tried it but keep on hitting "Too Many Variables" message. I have even change the config.fpw to mvcount 2400 but still does not work. For your info., I'm running this from my App. calling the specified request from my menu option.I have tried another way of doing this but it is much more tedious than the way you suggested. I have used ffconfig in the after FRX genearted phase and replace the header programatically. Any problem with this method? I still prefer your way, if you know what I have done wrongly appreciate if you let me know.....Thanks again.


Well, FoxFire! does produce an ENORMOUS number of memory variables while running (but 2400 seems a bit much). Try replacing the error handler with a routine which will send your memory variables to a file (DISPLAY MEMO TO FILE memory.txt NOCONSOLE). This might give you a clue as to what's in memory. If your app uses a lot of globals which are not used by Foxfire!, could you do a STORE TO and then RESTORE FROM?

Valerie