Re: FoxPro 2.6 Problem with wait windows
- From: "TonySper" <tsperduti@xxxxxxxxxxxxxxxxxxx>
- Date: Wed, 24 Jan 2007 17:06:40 -0500
Have you installed the patch for Fox Pro 2.6 as there is a problem
with 2.6 when the CPU's went over 300 speed. Even if you do install
this patch I think you would have to reassemble the program.
"PATCH_26.exe is a self-extracting executable file that updates the
FoxPro for Windows version 2.6a development environment and run-time
to eliminate startup errors encountered on computers operating at
clock speeds of about 333 MHZ and faster."
This may be effecting your timer.
TonySper
"Surrwin" <Surrwin@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:B28DE2AF-F88E-4D35-A57D-8FC2F7107F08@xxxxxxxxxxxxxxxx
Hello everyone,
I've been having this strange problem with my Fox Pro 2.6 application
which
i've just recently moved over to a newer machine running Windows NT
4.0
The issue is that whenever there is a wait window in the program that
has a
timeout it doesn't actually follow the alotted time. For example:
wait window "Not using error handler!" timeout .1
This message should only display for 1 millisecond but instead it
displays
and never goes away. I've set my time and date setting to exactly
what the
old machine was using and that is fine.
Also, we do not have the code for some of the programmings with the
same
problem so I was hoping there would be a non-code change solution.
Honestly i'm stumped. The machine is only a P2 450. The old machine
was a
P 100.
I've installed the processor speed patch and that didn't change
anything.
Please, if you have any ideas list them below. I need any help I get.
Thank you!
.
- Follow-Ups:
- Re: FoxPro 2.6 Problem with wait windows
- From: Surrwin
- Re: FoxPro 2.6 Problem with wait windows
- Prev by Date: Re: Rlock() & isrlocked() mystery: Solved
- Next by Date: Buffer over-run detected
- Previous by thread: Query deleted FoxPro records from .NET/Crystal Reports
- Next by thread: Re: FoxPro 2.6 Problem with wait windows
- Index(es):
Relevant Pages
|