开云体育

I've got a client that has been running an app
written in VFP6. It has been running fine for
several years. They recently upgraded to XP
Professional and it was still running. Now they
say it won't run. It starts then 'Goes away'.
It shows up if they check the task list as still
running. I've told them to try it on another machine
and it works on that one, which is also XP Prof.
I think it is getting to a point where a dialog
box comes up. Any ideas?

__________________________________
Do you Yahoo!?
Yahoo! Search - Find what youre looking for faster

Start simple - reinstall the VFP run-times.

- Chad J. Lemmer

I did that and ran windows update.

--- "Chad J. Lemmer" <cjlemmer@...> wrote:

Start simple - reinstall the VFP run-times.

- Chad J. Lemmer

----- Original Message -----
From: "Scott Sharpe" <ssharpee@...>
To: <madfox_vfp@...>
Sent: Thursday, March 04, 2004 11:42 AM
Subject: RE: [madfox_vfp] Problem Running VFP

I've got a client that has been running an app
written in VFP6. It has been running fine for
several years. They recently upgraded to XP
Professional and it was still running. Now they
say it won't run. It starts then 'Goes away'.
It shows up if they check the task list as still
running. I've told them to try it on another

machine

and it works on that one, which is also XP Prof.
I think it is getting to a point where a dialog
box comes up. Any ideas?

__________________________________
Do you Yahoo!?
Yahoo! Search - Find what you're looking for

faster

Yahoo! Groups Links

__________________________________
Do you Yahoo!?
Yahoo! Search - Find what youre looking for faster

What does the dialog box say?

--
Sonia Yaco

Anlex Computer Consulting LLC
Email: sy@...

Anlex Web Page:

The first step imports some data from an old legacy
system they still use. Then the dialog box just asks
if they want to continue. They never see the dialog
box. The imported files look the same and everything
works on another PC so I'm confident the data is not
an issue. I thought something might have happened to
the runtime files that would have stopped the dialog
box from functioning correctly, so I replaced the
run-time files. But that didn't help.



--- SY <sy@...> wrote:

What does the dialog box say?

--
Sonia Yaco

Anlex Computer Consulting LLC
Email: sy@...

Anlex Web Page:

__________________________________
Do you Yahoo!?
Yahoo! Search - Find what youre looking for faster

This was the solution to a similar problem I was having with an .EXE .
PRB: Application Appears Then Exits to Operating System
;en-us;132697&Product=fox

--
Sonia Yaco

Anlex Computer Consulting LLC
Email: sy@...

Anlex Web Page:

This program is not very complicated. It imports the
data, does some calculations and generates a report.
There is no form or menu. They just wanted a dialog
box to inform them that the data had been imported
with no problems. So I don't think I need a read
events in it.

--- SY <sy@...> wrote:

This was the solution to a similar problem I was
having with an .EXE .
PRB: Application Appears Then Exits to Operating
System

;en-us;132697&Product=fox

--
Sonia Yaco

Anlex Computer Consulting LLC
Email: sy@...

Anlex Web Page:

__________________________________
Do you Yahoo!?
Yahoo! Search - Find what youre looking for faster

Administrative rights needed for your program? (Creating folders, etc.)

Eric

No, this doesn't seem to be the problem either.
I've talked to them and verified they have all
the rights they need.

--- Eric Selje <eselje@...> wrote:

Administrative rights needed for your program?
(Creating folders, etc.)

Eric

__________________________________
Do you Yahoo!?
Yahoo! Search - Find what youre looking for faster

I had trouble with one app when the tempfiles folder specified in
config.fpw didn't exist. Could that be it?

Eric

Since the program still shows up in the task list, your Foxpro code is still
doing something. It seems like you're going to have to figure out just what
that something is, then determine how to fix it. You say there's no READ
EVENTS involved, so it seems like it's either waiting for input into the
dialog box, which for some reason isn't made visible, or it's stuck in an
infinite loop during the data import routine.

This would be easy to figure out if you could reproduce the problem on your
machine, but it gets to be a PITA when it only happens on a remote site,
without the Debugger available, depending on the customer to tell you what's
going on, etc. One thing I've found invaluable in such situations is to
include a Trace method in my apps which includes code like this:

lcFile = 'DEBUG'+RIGHT(DTOS(DATE()),4)+'.TXT'
lcText = TIME(1)+' '+TRANSFORM(PROGRAM(PROGRAM(-1)-1))+' '+lcText
STRTOFILE(lcText+CR,lcFile,.T.)

lcText is passed in as a parameter

I scatter calls to this a crucial points thruout the program, trying to
include helpful notes (including variable values) in the parameter string. I
then tell the user to run it to reproduce the problem and have them send me
the resulting DEBUGxxxxx.TXT file. Typical output might look like this:

01:12:24.25 ACECODECLASS.ECHANDLER register button clicked
01:12:24.26 ACECODECLASS.REGINIT Initializing. UserID=XX0000098
Etc.

In your case, you could stick in some strategic calls like this:

Trace("Ready to starting input routine...")
...
Trace("Input file opened.")
...
Trace("Data has been imported.")
...
Trace("Ready to show dialog")
nResult = MESSAGEBOX(...) or however you do this
Trace("Done with dialog. Result="+TRANSFORM(nResult)
Etc etc....

Looking at the trace output should at least let you know what point in the
program to focus on. If it gets to "ready to show dialog" and stops, you'll
know that it's a dialog display issue. Or you may end up rethinking your
statement that the data is not an issue...




--stein

Stein Goering
Arbutus Computer Services
17494 Merry Hill Rd
Richland Center, WI 53581

608.538.3820