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
_______________________________________________
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/4F358963.5090104@ggisoft.com
** 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.
Mike Copeland wrote on 2012-02-10:
> 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
>
Mike,
Fix the application.
If you are collecting data to later hand to a report, give them a progress
bar.
If the select statement is rather long, SET ESCAPE ON and allow VFP to show
the progress bar.
If the report is getting the data, it should be handed data since it takes
too long.
The UI thread is blocked, since VFP is not multi-threaded, selects that take
a long time will cause this behavior.
Tracy Pearson
PowerChurch Software
_______________________________________________
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/000d01cce83c$0efc2870$2cf47950$@powerchurch.com
** 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.
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.
Tell them to try window live mail. that's a huge dog that spends most its
life trying to update flags. Outlook was bad enough but that takes the cake.
I've not noticed VFP problems like that though. But I have noticed that all
that crap about 7 being faster to load and run is twoddle. Closing down is
so slow.
One thing, I think the behaviour you see is only when someone gets clicky.
Maybe they should get a coffee.
Al
-----Original Message-----
From: Mike Copeland
Sent: Friday, February 10, 2012 10: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.
_______________________________________________
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/805B90CADCBD44EF97D54FABBD2F74AA@gslredacer
** 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.
> Fix the application.
>
I would tend to agree that you need to provide some feedback for long
blocking operations.
--
Alan Bourke
alanpbourke (at) fastmail (dot) fm
_______________________________________________
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/1328952550.20763.140661035127153@webmail.messagingengine.com
** 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.
Thanks Tracy. We're working in that direction...using MySQL on the
backend for all data storage. Unfortunately there are still some tables
of data that are both large, and necessary. The errors usually (95% of
the time) happen when opening the DBF files or updating them. Oh, and
the fact that the server and the workstations are in different buildings
doesn't help...connected via aj virtual private network over the Internet.
Mike
-------- Original Message --------
Subject: Re: VFP + Windows 7
From: Tracy Pearson <tracy@powerchurch.com>
To: profoxtech@leafe.com
Date: 2/10/2012 3:36 PM
Mike Copeland wrote on 2012-02-10:
> 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
>
Mike,
Fix the application.
If you are collecting data to later hand to a report, give them a progress
bar.
If the select statement is rather long, SET ESCAPE ON and allow VFP to show
the progress bar.
If the report is getting the data, it should be handed data since it takes
too long.
The UI thread is blocked, since VFP is not multi-threaded, selects that take
a long time will cause this behavior.
Tracy Pearson
PowerChurch Software
[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/4F36396B.10707@ggisoft.com
** 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.
Thanks Kurt. Unfortunately the unresponsive messages usually trigger
while opening or updating DBF files on the server, which is in a
different building. The workstations connect via a VPN over the
Internet. We're working on moving all the data to a backend server,
which will resolve the problem except in the most extreme cases.
Mike
-------- Original Message --------
Subject: Re: VFP + Windows 7
From: Kurt Wendt <kurtwendt@waitex.com>
To: profoxtech@leafe.com
Date: 2/10/2012 3:36 PM
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/4F3639E1.2030906@ggisoft.com
** 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.
Al,
I've only had one occasion to even open Live Mail, but wow...was not
impressed! I was expecting (hoping for) Outlook Express with a face
lift...not even close!
I've had occasion to hang around the offices where this reboot-mania
happens, and what usually causes it is when someone makes a comment, out
loud, about how their "computer has frozen!"...usually someone of the
female persuasion.
Now, actually it's not frozen at all, just busy. But then a helpful
computer-guy-wannabe will pipe up and instruct everyone who is listening
that "...you just need to push that small button on the front of the
tower. Here, let me show you..."
I have a lot more trouble with end users who think they know all about
computers than I ever do with the machines, or the software, or the
other 99% of the humans involved.
Mike
-------- Original Message --------
Subject: Re: VFP + Windows 7
From: Allen <profox@gatwicksoftware.com>
To: profoxtech@leafe.com
Date: 2/10/2012 3:48 PM
Tell them to try window live mail. that's a huge dog that spends most its
life trying to update flags. Outlook was bad enough but that takes the cake.
I've not noticed VFP problems like that though. But I have noticed that all
that crap about 7 being faster to load and run is twoddle. Closing down is
so slow.
One thing, I think the behaviour you see is only when someone gets clicky.
Maybe they should get a coffee.
Al
-----Original Message-----
From: Mike Copeland
Sent: Friday, February 10, 2012 10: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.
[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/4F363B4A.50003@ggisoft.com
** 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.
Mike,
>> 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.<<
Maybe you should consider one of the multi-threaded techniques like:
1) ParallelFox from VFPX, http://vfpx.codeplex.com/wikipage?title=ParallelFox&referringTitle=Home
2) Christof Wollenhaupt's DMULT.DLL. http://foxpert.com/downloads.htm
This way you could spawn off the report and let the application continue. Even without the multi-threading you could
spawn off another VFP application to show just the report and let the user Alt-Tab back to the main application.
Rick
White Light Computing, Inc.
www.whitelightcomputing.com
www.swfox.net
www.rickschummer.com
_______________________________________________
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/004301cce8fb$14356260$3ca02720$@whitelightcomputing.com
** 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.
Thanks Rick, I appreciate the pointer. Not sure I want to invest much
time in trying to multithread though.
I've set up several virtual workstations for the time being, and am
moving all VFP work over to those until the data gets moved out of the
DBF files and the no response problem goes away...mostly.
Mike
-------- Original Message --------
Subject: Re: VFP + Windows 7
From: Rick Schummer <profox@whitelightcomputing.com>
To: profoxtech@leafe.com
Date: 2/11/2012 2:23 PM
Mike,
>> 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.<<
Maybe you should consider one of the multi-threaded techniques like:
1) ParallelFox from VFPX, http://vfpx.codeplex.com/wikipage?title=ParallelFox&referringTitle=Home
2) Christof Wollenhaupt's DMULT.DLL. http://foxpert.com/downloads.htm
This way you could spawn off the report and let the application continue. Even without the multi-threading you could
spawn off another VFP application to show just the report and let the user Alt-Tab back to the main application.
Rick
White Light Computing, Inc.
www.whitelightcomputing.com
www.swfox.net
www.rickschummer.com
[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/4F36D9B1.7070100@ggisoft.com
** 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.