>>>>>Tried that too. No Luck.
>>>>>
>>>>>Let me give a little more background on the problem.
>>>>>
>>>>>When I exit the application and DISP STAT or DISP MEMORY I can see that some of the variables and/or objects are still active. I can do CLOSE ALL and CLEAR ALL and all the variables and objects are gone but I still can't build the application again.
>>>>>
>>>>>I have tried every command I know (and I have been in the Fox business for 10 years), and still can't seem the clear the application object from memory.
>>>>>
>>>>>I AM BAFFELED..........
>>>>>
>>>>>
>>>>>
>>>>>>CLEAR PROGRAM ?
>>>>>>
>>>>>>Vlad
>>>>>>
>>>>>>>I have already tried "SET CLASSLIB TO" with no luck. Any other suggestion would be appreciated.
>>>>>>>
>>>>>>>Thanks
>>>>>>>
>>>>>>>>This is because you set library to... without clearing the library from memory when is no longer needed.
>>>>>>>>
>>>>>>>>Vlad
>>>>>>>>
>>>>>>>>>I have the following code in the init method of a form.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>SET CLASSLIB TO controls IN SEA.APP ALIAS lcl_class ADDITIVE
>>>>>>>>>THIS.AddObject("Grd_Orders","or_returns_pick_orno_grid")
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>Everyting works fine but when I return to the project manager and try to build the app the next time I get the following message:
>>>>>>>>>
>
>Nothing shows up in the debugger.
>>>>>>>>>Object File "D:\Appdevelopment\Sea\Sea.app" is in use and cannot be removed from memory.
>>>>>>>>>
>>>>>>>>>Does anyone know what's going on.
>>>>
>>>>
>>>>I often run into this problem when a procedure file that is built into the app is still active. With visual fox we can now set a seemingly unlimited number of prg's as procedure files (set procedure to <> additive). If the procedure file is still active and is also part of the app file, the app will not compile. What I find that seems to work well is a simple SET PROCEDURE TO from the command window. CLEAR ALL in the app doesn't always work as well as it does from the command (global object references etc still active in the top level main program).
>>>>
>>>>Bob
>>>
>>>Thanks for the suggestions, but no cigar. Do you know of any way to display all active objects...when I DISPLAY STATUS, SYS(18) and _CUROBJ with no luck. I can see no evidence that any object is in use. Thanks again for your time.
>>>
>>>Lamar
>>
>>In VFP5 you can see them in Debugger.
>>
>>Vlad


I've had this problem many times. I have a macro programmed to one of m function keys that issues a CLOSE ALL, RELE ALL, then CLEAR ALL. SOMETIMES I find I still neeed to issue a SET CLASSLIB TO. If you're using the TasTraders template, before issuing the RELE ALL, you might also consider issuing a oApp.cleanup(), that works well too.

HTH