VFP6 runtime crashes on XP

As I feared. My SBT VP10 client is bringing in another Accpac dealer
tomorrow to examine their system. To look into upgrading to Pro Series. Now
they have a very modified VP10 system, so it won't be cheap. But the VP10
client is so mad at the runtime crashes, he might just do it. Which means I
outta work.

To recap: My VP10 build 110 client uses XP Pro workstations, Small Business
Server 2003 for VP10 application/data. Most workstations get a couple of
VFP6 runtime crashes a day. And they can't tell me if there's a pattern.
Seems to happen most anywhere. Here's the last recorded crash:
http://www.dennisallen.com/vfperror.pdf

I've already tried to install my VFP6 SP5 runtime on a workstation. No
change. I heard that VFP6 might have ActiveX giving XP or SBS problems.
Question. Does VFP6 have ActiveX components? If so, how would VP10 use
them? Can they be fixed/removed?

The only other thing I can think of the Okida DM printer. Most workstations
print sales orders to it. Maybe the workstations need to upgrade to XP
drivers?

If anyone else has any more suggestions, I'd appreciate any advice...Dennis

Rick
Mon May 24 16:41:16 CDT 2004

Dennis,
Since SBT is trapping the error, it isn't a C0...05 error, so it's =
curious that it doesn't log or provide more information than "You need =
to close" - it's all available to VFP. It obviously needs substantially =
better error handling. (It could even be a syntax error in some expanded =
macro code!)

VFP itself doesn't use any ActiveX controls, but the application could =
be using any number of them, from common dialogs, to date pickers, to =
graphing, etc. (and these are just the MS supplied ones!). The install =
routine should give you a clue as to whether any are used.

A printer driver could indeed be the problem, as well as Virus checkers =
(and the workstations OR the server) that aren't configured properly. It =
could even be bad network connections - bad cables, NICs, hubs, routers, =
switches, etc.

Without more information on the "real" errors happening, it's really a =
total guess on what to "fix".

Rick

"Dennis Allen" <dennis@dennisallen.com> wrote in message =
news:OSEYlrcQEHA.3852@TK2MSFTNGP10.phx.gbl...
> As I feared. My SBT VP10 client is bringing in another Accpac dealer
> tomorrow to examine their system. To look into upgrading to Pro =
Series. Now
> they have a very modified VP10 system, so it won't be cheap. But the =
VP10
> client is so mad at the runtime crashes, he might just do it. Which =
means I
> outta work.
>=20
> To recap: My VP10 build 110 client uses XP Pro workstations, Small =
Business
> Server 2003 for VP10 application/data. Most workstations get a couple =
of
> VFP6 runtime crashes a day. And they can't tell me if there's a =
pattern.
> Seems to happen most anywhere. Here's the last recorded crash:
> http://www.dennisallen.com/vfperror.pdf
>=20
> I've already tried to install my VFP6 SP5 runtime on a workstation. =
No
> change. I heard that VFP6 might have ActiveX giving XP or SBS =
problems.
> Question. Does VFP6 have ActiveX components? If so, how would VP10 =
use
> them? Can they be fixed/removed?
>=20
> The only other thing I can think of the Okida DM printer. Most =
workstations
> print sales orders to it. Maybe the workstations need to upgrade to =
XP
> drivers?
>=20
> If anyone else has any more suggestions, I'd appreciate any =
advice...Dennis
>=20
>

Dennis
Mon May 24 21:22:24 CDT 2004


"Rick Bean" <rgbean@unrealmelange-inc.com> wrote in message
news:uJpGFhdQEHA.2976@TK2MSFTNGP10.phx.gbl...
Dennis,
> Since SBT is trapping the error, it isn't a C0...05 error, so it's curious
that it doesn't log or provide more information than "You need to close" -
it's all available to VFP. It obviously needs substantially better error
handling. (It could even be a syntax error in some expanded macro code!)

I don't think it's SBT. SBT has it's own error handler and would tell you
to 'quit to main menu', not just die. I think it's XP handling the problem
with the VFP6 runtime by shutting it down.

>VFP itself doesn't use any ActiveX controls, but the application could be
using any number of them, from common dialogs, to date pickers, to graphing,
etc. (and these are just the MS supplied ones!). The install routine should
give you a clue as to whether any are used.

It the VFP6 runtime, but SBT has their own install. Can't tell what
installed where.

> A printer driver could indeed be the problem, as well as Virus checkers
(and the workstations OR the server) that aren't configured properly. It
could even be bad network connections - bad cables, NICs, hubs, routers,
switches, etc.

Well, they didn't have problems until after they installed the Small
Business Server 2003.

Anders
Tue May 25 10:13:18 CDT 2004

The messagebox Nicole captured isn't an XP OS error message. Nor is it a
system message from VFP.
-Anders

"Dennis Allen" <dennis@dennisallen.com> wrote in message
news:uMUAc8fQEHA.556@tk2msftngp13.phx.gbl...
>
> "Rick Bean" <rgbean@unrealmelange-inc.com> wrote in message
> news:uJpGFhdQEHA.2976@TK2MSFTNGP10.phx.gbl...
> Dennis,
> > Since SBT is trapping the error, it isn't a C0...05 error, so it's
curious
> that it doesn't log or provide more information than "You need to close" -
> it's all available to VFP. It obviously needs substantially better error
> handling. (It could even be a syntax error in some expanded macro code!)
>
> I don't think it's SBT. SBT has it's own error handler and would tell you
> to 'quit to main menu', not just die. I think it's XP handling the
problem
> with the VFP6 runtime by shutting it down.
>
> >VFP itself doesn't use any ActiveX controls, but the application could be
> using any number of them, from common dialogs, to date pickers, to
graphing,
> etc. (and these are just the MS supplied ones!). The install routine
should
> give you a clue as to whether any are used.
>
> It the VFP6 runtime, but SBT has their own install. Can't tell what
> installed where.
>
> > A printer driver could indeed be the problem, as well as Virus checkers
> (and the workstations OR the server) that aren't configured properly. It
> could even be bad network connections - bad cables, NICs, hubs, routers,
> switches, etc.
>
> Well, they didn't have problems until after they installed the Small
> Business Server 2003.
>
>

Rick
Tue May 25 10:15:05 CDT 2004

Dennis,
The "message box" in the .PDF at your link is definitely not a native =
VFP or XP one - I've gotten enough of both - so that only leaves SBT. =
I'm sure the designers of SBT know that certain errors can't be =
programmatically handled (e.g. loss of network connection), but they =
should at least provide what ever information that is available.

In the SBT install, look for an .INI file or Config file that lists the =
files installed. Worse case, you could get on one of the many "watcher" =
programs available that take snapshots of the registry and drive =
directories before and after the install and list what's been added, =
changed and deleted. (I use PC Magazine's InCtrl5, but there are other =
freeware/shareware and commercial packages out there.) You might have to =
install it on multiple systems to get a clear picture of what's =
installed and updated, but it's always good to know. Of course you could =
also just ask AccPac what they install - they might know! <g>

Was SBS installed on the current hardware, or a new system. If it was =
the current, they probably needed to do some upgrading of memory, disks, =
NICs, etc., and a new system would introduce a number of variables into =
the network setup.

Rick

"Dennis Allen" <dennis@dennisallen.com> wrote in message =
news:uMUAc8fQEHA.556@tk2msftngp13.phx.gbl...
>=20
> "Rick Bean" <rgbean@unrealmelange-inc.com> wrote in message
> news:uJpGFhdQEHA.2976@TK2MSFTNGP10.phx.gbl...
> Dennis,
> > Since SBT is trapping the error, it isn't a C0...05 error, so it's =
curious
> that it doesn't log or provide more information than "You need to =
close" -
> it's all available to VFP. It obviously needs substantially better =
error
> handling. (It could even be a syntax error in some expanded macro =
code!)
>=20
> I don't think it's SBT. SBT has it's own error handler and would tell =
you
> to 'quit to main menu', not just die. I think it's XP handling the =
problem
> with the VFP6 runtime by shutting it down.
>=20
> >VFP itself doesn't use any ActiveX controls, but the application =
could be
> using any number of them, from common dialogs, to date pickers, to =
graphing,
> etc. (and these are just the MS supplied ones!). The install routine =
should
> give you a clue as to whether any are used.
>=20
> It the VFP6 runtime, but SBT has their own install. Can't tell what
> installed where.
>=20
> > A printer driver could indeed be the problem, as well as Virus =
checkers
> (and the workstations OR the server) that aren't configured properly. =
It
> could even be bad network connections - bad cables, NICs, hubs, =
routers,
> switches, etc.
>=20
> Well, they didn't have problems until after they installed the Small
> Business Server 2003.
>=20
>

Dennis
Wed May 26 22:23:28 CDT 2004

Well, vfpw.exe is the VFP6 runtime launcher. The dialog box displays the
icon assigned to the exe.

An SBT dealer came in and tweaked the SBS system. If it works, I'll try to
find out what he did...Dennis

"Anders Altberg" <x_pragma@telia.com> wrote in message
news:%237QlxpmQEHA.628@TK2MSFTNGP11.phx.gbl...
> The messagebox Nicole captured isn't an XP OS error message. Nor is it a
> system message from VFP.
> -Anders
>
> "Dennis Allen" <dennis@dennisallen.com> wrote in message
> news:uMUAc8fQEHA.556@tk2msftngp13.phx.gbl...
> >
> > "Rick Bean" <rgbean@unrealmelange-inc.com> wrote in message
> > news:uJpGFhdQEHA.2976@TK2MSFTNGP10.phx.gbl...
> > Dennis,
> > > Since SBT is trapping the error, it isn't a C0...05 error, so it's
> curious
> > that it doesn't log or provide more information than "You need to
close" -
> > it's all available to VFP. It obviously needs substantially better error
> > handling. (It could even be a syntax error in some expanded macro code!)
> >
> > I don't think it's SBT. SBT has it's own error handler and would tell
you
> > to 'quit to main menu', not just die. I think it's XP handling the
> problem
> > with the VFP6 runtime by shutting it down.
> >
> > >VFP itself doesn't use any ActiveX controls, but the application could
be
> > using any number of them, from common dialogs, to date pickers, to
> graphing,
> > etc. (and these are just the MS supplied ones!). The install routine
> should
> > give you a clue as to whether any are used.
> >
> > It the VFP6 runtime, but SBT has their own install. Can't tell what
> > installed where.
> >
> > > A printer driver could indeed be the problem, as well as Virus
checkers
> > (and the workstations OR the server) that aren't configured properly. It
> > could even be bad network connections - bad cables, NICs, hubs, routers,
> > switches, etc.
> >
> > Well, they didn't have problems until after they installed the Small
> > Business Server 2003.
> >
> >
>

Frank
Thu May 27 22:50:24 CDT 2004

"Dennis Allen" <dennis@dennisallen.com> wrote in news:uMUAc8fQEHA.556
@tk2msftngp13.phx.gbl:

> Well, they didn't have problems until after they installed the Small
> Business Server 2003.

Hi Dennis,

Since the problem started after the SBS install, the first thing I'd do is
replace the nic in the SBS server.

FWIW, I manage a few SBT VP10 systems and have never seen a message like
this. I suspect it was caused by a catastrophic hardware error (such as
the nic in the server).

Frank