>>Here are some logs if I just open the application, then only open the form and immediately close it, then close the application:
>>
>>Line 140: 2017.03.01 17:11:26.261 ADMIN NAOMI 5 SysManager application menu is now launched... Memory currently used is 2264 SYSMANAGER()
>> Line 145: 2017.03.01 17:11:28.504 ADMIN NAOMI 5 Booking_Schedule form loading... Memory currently used is 3340 BOOK_SCHEDULE.LOAD() WEBPAGES
>> Line 164: 2017.03.01 17:11:32.265 ADMIN NAOMI 5 Booking_Schedule form destroying... Memory currently used is 5893 BOOK_SCHEDULE.DESTROY() WEBPAGES
>> Line 165: 2017.03.01 17:11:34.183 ADMIN NAOMI 5 SysManager application is closing... Memory currently used is 3371 SYSMANAGER() WEBPAGES
>> Line 171: 2017.03.01 17:11:35.818 ADMIN NAOMI 5 SysManager application is closing in development mode... Memory currently used is 2516 SYSMANAGER()
>>
>>----------------------------
>>The users are doing lots and lots of work in that particular form. If only opening the form and closing shows such a difference in memory (I added inkey(1) before that logging line in Destroy), then the form does look like it's leaking the memory, do you agree? And if so, it may very well be related to that ocx control.
>
>> before that logging line in Destroy
>
>The Destroy event is part of the form, so the form is in memory while Destroy is executing, even Unload is executed after that, and all other internal object's destroy event.
>
>You can see this for the sequence of those events to see that a lot continue to happen:
>http://fox.wikis.com/wc.dll?Wiki~FormEventSequence
>
>The only real final measure is like the examples I gave, once the form is released, so this measurement can't be done inside the form, and this is true for the loading (can't use load/init events) and unload (destroy/unload events). This 2 measures must be done outside the form.

I can add the logging in the menu call that does the instantiation of the form. The form is not modal.