Hmm, I'm curious why yours did not work the same. I still have the lngAddr, and am still passing the addressof by value (from the onclick sub). I don't know why it didn't work on yours. Maybe because I'm running WinXPro w/ 2003 ... and you're running something different? In either case, the variable should still work the same as the actual function call because the values should be the same.
ANYHOW... despite the error after the code window appears, this is exactly what I needed and I'm going to use this code, in lieu of all the other suggestions. I thank you all for your help, especially my man John.
All the suggestions were valid, I just think it's more accurate (and useful) to know exactly when a window closes. And John, since you seem to be knowledgable about API calls, I'm sure you know how much I appreciate getting that window handle and having a wiindowproc to work with.
Furthermore, Do you know if it's possible to actually define the proc, or do I have have to use VBAs stagnant/default proc?
This is more of a trivial question then something I'm going to use (because I have no use for it as of yet). I will be around if you guys have any questions for me ---
Thank you all again,
Modest
ANYHOW... despite the error after the code window appears, this is exactly what I needed and I'm going to use this code, in lieu of all the other suggestions. I thank you all for your help, especially my man John.
All the suggestions were valid, I just think it's more accurate (and useful) to know exactly when a window closes. And John, since you seem to be knowledgable about API calls, I'm sure you know how much I appreciate getting that window handle and having a wiindowproc to work with.
Furthermore, Do you know if it's possible to actually define the proc, or do I have have to use VBAs stagnant/default proc?
Thank you all again,
Modest
Last edited: