>>I'm not sure about that. Actually, trapping on WM_CREATE is a standard Win32 apps. I think Borland C++ also have an access to the window (and child window) procedure. It's just I don't know a "how to".
>>Another (bad) idea is to hook the window creation <*g*> then destroy it from the hook. Or can you just check everything before the constructor ?
>
>Yes if I can't find a solution relatively soon I will add the check for data connection before I even start thinking about initiating the form.

Sorry about that. Hope you can find a good solution.

Regards