Skip to main content

[Migrated content. Thread originally posted on 08 March 2005]

I having a memory issue in my programs. When i close a child program called from a father program and i call it again, the focus, the data fields, all is equal when i close it the first time. Is like the memory isnt flushed after the acu-screen-exit and the Cancel "Child Program". and if i delete de .acu file of the child program i still can calling the child until the father is closed.

The real problem occurs when i compile the child to set some modifications and i have to close all and reopen the father to see the changes, and if the father last too much opening the lost time is big. I test it in three different PCs and at the first time i think that can be an issue of Windows XP managing memory, but it starts happening time ago I install Windows XP.

If someone can tell me if I'm not the only one or what is the problem it will "very time saving"

Thanks

[Migrated content. Thread originally posted on 08 March 2005]

I having a memory issue in my programs. When i close a child program called from a father program and i call it again, the focus, the data fields, all is equal when i close it the first time. Is like the memory isnt flushed after the acu-screen-exit and the Cancel "Child Program". and if i delete de .acu file of the child program i still can calling the child until the father is closed.

The real problem occurs when i compile the child to set some modifications and i have to close all and reopen the father to see the changes, and if the father last too much opening the lost time is big. I test it in three different PCs and at the first time i think that can be an issue of Windows XP managing memory, but it starts happening time ago I install Windows XP.

If someone can tell me if I'm not the only one or what is the problem it will "very time saving"

Thanks
Sounds like you have your program in stay resident mode. Any chance your program has the IS RESIDENT clause in the source?

[Migrated content. Thread originally posted on 08 March 2005]

I having a memory issue in my programs. When i close a child program called from a father program and i call it again, the focus, the data fields, all is equal when i close it the first time. Is like the memory isnt flushed after the acu-screen-exit and the Cancel "Child Program". and if i delete de .acu file of the child program i still can calling the child until the father is closed.

The real problem occurs when i compile the child to set some modifications and i have to close all and reopen the father to see the changes, and if the father last too much opening the lost time is big. I test it in three different PCs and at the first time i think that can be an issue of Windows XP managing memory, but it starts happening time ago I install Windows XP.

If someone can tell me if I'm not the only one or what is the problem it will "very time saving"

Thanks
Sounds like you have your program in stay resident mode. Any chance your program has the IS RESIDENT clause in the source?

[Migrated content. Thread originally posted on 08 March 2005]

I having a memory issue in my programs. When i close a child program called from a father program and i call it again, the focus, the data fields, all is equal when i close it the first time. Is like the memory isnt flushed after the acu-screen-exit and the Cancel "Child Program". and if i delete de .acu file of the child program i still can calling the child until the father is closed.

The real problem occurs when i compile the child to set some modifications and i have to close all and reopen the father to see the changes, and if the father last too much opening the lost time is big. I test it in three different PCs and at the first time i think that can be an issue of Windows XP managing memory, but it starts happening time ago I install Windows XP.

If someone can tell me if I'm not the only one or what is the problem it will "very time saving"

Thanks
Well was a problem with a thread called from the child program that dont let us cancel the child program.

Thanks anyway for the tip, it was useful to reach the answer :P
Terms & ConditionsAccessibility statement