Hi,

I'm sure there's an easy way to get around this and that its more a Windows thing that an Elevate thing...I have a program where an EDBScript loads an SQL script produced by the Reverse-Engineer option in EDManager with the Include Progress checked.

The script works fine and creates the tables / data.

The PercentDone and StatusMessage also work well. The problem is if I lclick on the forms title bar it stops refreshing and the application shows the windows message '(Not Responding)'.

This still completes perfectly and then I gain control back to the form after, but is there a way to stop windows thinking the application is (Not Responding) when I click on the form. It might make clients think the program has crashed when it's really working perfectly?

Thanks,

Phil.

I guess I should probably run the process in another thread, that should fix it, but I thought there might be an easier way.

Yep, wacking it in a thread works perfecty All good!

Philip,

have you tried application.processmessages within the progress event
handler?

Uli

Philip,

<< The PercentDone and StatusMessage also work well. The problem is if I
lclick on the forms title bar it stops refreshing and the application shows
the windows message '(Not Responding)'. >>

My suggestion would be the same as Uli's - use Application.ProcessMessages
to pump the message queue and allow the click to be processed.

--
Tim Young
Elevate Software
www.elevatesoft.com

Thanks Uli & Tim.... Yes that works just as well and so have scrapped the Thread, keeps life simple!