0

Hi,

I have a custom control that we delevoped, I Added a new property to the control hence breaking compatability. I re-compiled all applications with the new version of the OCX and released them to TEST. All applications passed testing and was delivered to our client. All these app's with the new registered OCX now come up with "Runtime Error 7: Out Of Memory" :evil: Does anyone know why it would work on my machines then error on the clients machine. Windows 2000 is the O/S.

Cheers

2
Contributors
1
Reply
2
Views
13 Years
Discussion Span
Last Post by maheshsayani
0

Hi,

I have a custom control that we delevoped, I Added a new property to the control hence breaking compatability. I re-compiled all applications with the new version of the OCX and released them to TEST. All applications passed testing and was delivered to our client. All these app's with the new registered OCX now come up with "Runtime Error 7: Out Of Memory" :evil: Does anyone know why it would work on my machines then error on the clients machine. Windows 2000 is the O/S.

Cheers

Once you completed using the control in the code try to kill the object using nothing.
I mean to say that in the form unload event try to kill objects (Use set <object,OCX control> = nothing) I think it will work

This topic has been dead for over six months. Start a new discussion instead.
Have something to contribute to this discussion? Please be thoughtful, detailed and courteous, and be sure to adhere to our posting rules.