Hi Neil,

I Know. I've seen that solution (yours ?). However I found the solution of having an extra FLL not suitable for my applications (To be honest I've found that the FLL was quite large in size for just one function). I distribute standard software troughout the country and deliver support by e-mail. If I can avoid to use a thrid party DLL i'll gladly do. Not that I don't trust this to be errorfree, but since I've experienced some nasty problems with Crystal Reports DLLs in combination with NT 4.0 and VFP 6.0 sp3, I'd be glad if I can eliminate every DLL (or FLL) to be the problem.

Aside from this, I've manage to simulate a resize-event pretty close now with VFP only code and the use of timers. The only way I'm going to step off this method is either by moving to top-level forms (which have their own problems to overcome) or VFP providing a way to bind code on the destop resize event.

Walter,

>You can use the VFPEvent FLL in the files section to trap resize events on the desktop. This hooks both the VFP event handler and the Window message queue in VFP so their is the potential for monitoring things like activation events amongst others.