Mike - I know what you mean by the Window becoming "Cloudy" - as I have

also seen that in Vista (the OS on my laptop). So - I think that thing

actually started in the Vista days - maybe a BAD thing to have carried

over to Win7!

I use 3D animation SW - and the really complex ones (like 3DS Max) - are

HUGE and take up TONS of resources - and a LONG time to Load (really -

time to switch my laptop to a bootable SSD). Well - the Logo/Splash

screen comes up - and it sits there for a LONG time (although - in the

lower left - its constantly running thru all these DLL's that it is

loading - so you know SOMETHING is happening). But, as you mentioned -

if I try and touch that splash screen - or possibly attempt to touch &

drag it - it goes Cloudy!

I know this may be a Pain - but, what about sending the record

manipulation code - if its an SQL - to another Form that could pop-up,

and put a Timer on that Form - and have the timer make some kind of

updates on the Form - I don't know - simulate a Big Clock or something)

- and maybe by having this form DOING Something - maybe it could inform

your Users as WELL as Informing Win7 that its Not just

Sitting-on-its-Arse-Doing-Nothing!

Anyway - there's my WAG for ya...

-K-

-----Original Message-----

From: profoxtech-bounces@leafe.com [mailto:profoxtech-bounces@leafe.com]

On Behalf Of Mike Copeland

Sent: Friday, February 10, 2012 4:17 PM

To: profoxtech@leafe.com

Subject: VFP + Windows 7

Many applications (not just VFP) when run on Windows 7 trigger display

of the "Not responding" status message on the application's title bar if

the application gets busy for an extended period. And, depending on what

you click on at that point, the "offending" window may become "shaded"

sort of a milky white...I guess it's Windows 7's attempt at showing that

the program is in distress or something.

Usually it's an issue with running reports in VFP....lots of data

flowing back and forth between server and workstation...more than 10

seconds elapses and the dreaded "Not Responding" is displayed.

This, not surprisingly, causes concern with the end user.

Most users assume this means "locked up" and start doing things they've

always been trained to do...reboot at all costs. Obviously this is not a

good thing if dbf files are open at the time, and a time-waster.

So, my point is this: Does anyone know how to either

a) turn this stupid error message off completely, or

b) extend the Windows 7 timer to be a little more lenient?

Yes, it also happened with XP, and 2000, too, but they seemed to be a

LOT more generous before declaring a crisis!

(And, yes, I know that end-user training is part of the solution...it's

just that even after being told to "be patient...it's okay", the jokes

and snide comments about the VFP application "is using a walker," "needs

some Viagra," etc., are getting old.)

Thanks for any WAGs or wisdom!

Mike

[excessive quoting removed by server]

_______________________________________________

Post Messages to: ProFox@leafe.com

Subscription Maintenance: http://leafe.com/mailman/listinfo/profox

OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech

Searchable Archive: http://leafe.com/archives/search/profox

This message: http://leafe.com/archives/byMID/profox/289EA162F5642645B5CF64D624C66A140B7CE9A5@us-ny-mail-002.waitex.net

** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.