Fatal Error

Mark,
What kind of "fatal" error are you encountering? C0...05 - These are =
system errors that while VFP can be notified of them, there is no way to =
recover from them, as the OS has already caused the task to die to =
protect itself!

There are many causes, including older versions of VFP, printer and =
video drivers, viruses and virus checkers, screen savers, hardware =
(including memory).

To start your evaluation, what version and service pack are you using? =
(e.g. 5.0 SP3, 6.0 SP5, 7.0 SP1, 8.0) What OSs is this happening on and =
how much memory are they running with? What else is running on the =
system? (e.g. Word, Outlook, Excel, etc.)

Rick

"Mark Kirchner" <markkirchner@lvcm.com> wrote in message =
news:3f5f50e5$1@tnews.web.dev-archive.com...
> Does anyone have any suggestions on how to track down a fatal error? =
Why
> does VFP report a fatal error anyway? I have error trapping and if =
it's an
> error in my code, why doesn't it get sent to my error trapping =
routine?
>=20
> The line of code the fatal error reports is the READ EVENTS in my =
main.prg.
> Main.prg is my "main" startup prg and goes like this:
>=20
> * initialization code
> do form main
> read events
>=20
> Then my main form sets up my main buttons and calls all the other =
forms and
> prgs.
> When it does happen, it seems to be when exiting off one or two =
particular
> forms.
>=20
> There are about 25 users on the system. The backend is SQL Server. I =
use
> remote views and SQL Pass through.
> Not all users get the error and it is sporadic.
> Usually the users are working for hours before it happens.
> However, I am not able to reproduce it here on my test environment.
>=20
> Could it have anything to do with memory?
>=20
> Thanks.
>=20
> Mark
>=20
>

I'm using VFP 8.0. The systems are Windows XP Pro and have at least 128MB
memory, most more. The majority of the machines are pretty new. The error
code is C0000005. As far as other software, mostly standard Microsoft office
products along with Norton anti-virus.
Mark

"Rick Bean" <rgbean@NOSPAMmelange-inc.com> wrote in message
news:3f5f5995$1@tnews.web.dev-archive.com...
Mark,
What kind of "fatal" error are you encountering? C0...05 - These are system
errors that while VFP can be notified of them, there is no way to recover
from them, as the OS has already caused the task to die to protect itself!

There are many causes, including older versions of VFP, printer and video
drivers, viruses and virus checkers, screen savers, hardware (including
memory).

To start your evaluation, what version and service pack are you using? (e.g.
5.0 SP3, 6.0 SP5, 7.0 SP1, 8.0) What OSs is this happening on and how much
memory are they running with? What else is running on the system? (e.g.
Word, Outlook, Excel, etc.)

Rick

"Mark Kirchner" <markkirchner@lvcm.com> wrote in message
news:3f5f50e5$1@tnews.web.dev-archive.com...
> Does anyone have any suggestions on how to track down a fatal error? Why
> does VFP report a fatal error anyway? I have error trapping and if it's an
> error in my code, why doesn't it get sent to my error trapping routine?
>
> The line of code the fatal error reports is the READ EVENTS in my
main.prg.
> Main.prg is my "main" startup prg and goes like this:
>
> * initialization code
> do form main
> read events
>
> Then my main form sets up my main buttons and calls all the other forms
and
> prgs.
> When it does happen, it seems to be when exiting off one or two particular
> forms.
>
> There are about 25 users on the system. The backend is SQL Server. I use
> remote views and SQL Pass through.
> Not all users get the error and it is sporadic.
> Usually the users are working for hours before it happens.
> However, I am not able to reproduce it here on my test environment.
>
> Could it have anything to do with memory?
>
> Thanks.
>
> Mark
>
>

On Wed, 10 Sep 2003 09:18:05 -0700, "Mark Kirchner"
<markkirchner@lvcm.com> wrote:

>Does anyone have any suggestions on how to track down a fatal error? Why
>does VFP report a fatal error anyway? I have error trapping and if it's an
>error in my code, why doesn't it get sent to my error trapping routine?

Check out this topic:
http://fox.wikis.com/wc.dll?Wiki~c0000005Error~VFP

Tamar

Thanks for your input Rick.

So what we're saying is something external to my software on the users
workstation is conflicting with my software and is causing the fatal error.
And there is no real way of knowing where the conflict is except by trial
and error and experience and persons like yourself who help point us in the
right direction.

Mark

"Rick Bean" <rgbean@NOSPAMmelange-inc.com> wrote in message
news:3f6072d0$1@tnews.web.dev-archive.com...
Mark,
It's CRITICAL that if there is a Virus checker running on a workstation or
server that it be configured to NOT actively check standard FoxPro files
(.DBF, .FPT, .CDX) and on developer systems all the other file types. (The
basic information in the following article also applies to other AV apps
depending on how they are implemented and how they can be configured.)

http://support.microsoft.com/default.aspx?scid=kb;en-us;321550 - "HOWTO:
Optimize Visual FoxPro Applications While Using Norton AntiVirus 2002"

I tend to specify a minimum of 256MB for VFP 8.0 applications and more if
the users are running anything else at the time the app is running.

Also check for updates on your printer and/or video drivers - especially if
they aren't using XP explicit drivers.

Rick

"Mark Kirchner" <markkirchner@lvcm.com> wrote in message
news:3f60113a$1@tnews.web.dev-archive.com...
> I'm using VFP 8.0. The systems are Windows XP Pro and have at least 128MB
> memory, most more. The majority of the machines are pretty new. The error
> code is C0000005. As far as other software, mostly standard Microsoft
office
> products along with Norton anti-virus.
> Mark
>
>
>
>
> "Rick Bean" <rgbean@NOSPAMmelange-inc.com> wrote in message
> news:3f5f5995$1@tnews.web.dev-archive.com...
> Mark,
> What kind of "fatal" error are you encountering? C0...05 - These are
system
> errors that while VFP can be notified of them, there is no way to recover
> from them, as the OS has already caused the task to die to protect itself!
>
> There are many causes, including older versions of VFP, printer and video
> drivers, viruses and virus checkers, screen savers, hardware (including
> memory).
>
> To start your evaluation, what version and service pack are you using?
(e.g.
> 5.0 SP3, 6.0 SP5, 7.0 SP1, 8.0) What OSs is this happening on and how much
> memory are they running with? What else is running on the system? (e.g.
> Word, Outlook, Excel, etc.)
>
> Rick
>
> "Mark Kirchner" <markkirchner@lvcm.com> wrote in message
> news:3f5f50e5$1@tnews.web.dev-archive.com...
> > Does anyone have any suggestions on how to track down a fatal error? Why
> > does VFP report a fatal error anyway? I have error trapping and if it's
an
> > error in my code, why doesn't it get sent to my error trapping routine?
> >
> > The line of code the fatal error reports is the READ EVENTS in my
> main.prg.
> > Main.prg is my "main" startup prg and goes like this:
> >
> > * initialization code
> > do form main
> > read events
> >
> > Then my main form sets up my main buttons and calls all the other forms
> and
> > prgs.
> > When it does happen, it seems to be when exiting off one or two
particular
> > forms.
> >
> > There are about 25 users on the system. The backend is SQL Server. I use
> > remote views and SQL Pass through.
> > Not all users get the error and it is sporadic.
> > Usually the users are working for hours before it happens.
> > However, I am not able to reproduce it here on my test environment.
> >
> > Could it have anything to do with memory?
> >
> > Thanks.
> >
> > Mark
> >
> >
>
>

Mark,
Yes, unfortunately that's correct in many of the situations. While the =
VFP 8.0 SP1 that's scheduled for the end of the month may help a few =
situations, it's isn't going to fix "system" problems. (See Ken Levy's =
latest update info at http://msdn.microsoft.com/vfoxpro/letters.)

Rick

"Mark Kirchner" <markkirchner@lvcm.com> wrote in message =
news:3f60ddf4$1@tnews.web.dev-archive.com...
> Thanks for your input Rick.
>=20
> So what we're saying is something external to my software on the users
> workstation is conflicting with my software and is causing the fatal =
error.
> And there is no real way of knowing where the conflict is except by =
trial
> and error and experience and persons like yourself who help point us =
in the
> right direction.
>=20
> Mark
>=20
>=20
>=20
> "Rick Bean" <rgbean@NOSPAMmelange-inc.com> wrote in message
> news:3f6072d0$1@tnews.web.dev-archive.com...
> Mark,
> It's CRITICAL that if there is a Virus checker running on a =
workstation or
> server that it be configured to NOT actively check standard FoxPro =
files
> (.DBF, .FPT, .CDX) and on developer systems all the other file types. =
(The
> basic information in the following article also applies to other AV =
apps
> depending on how they are implemented and how they can be configured.)
>=20
> http://support.microsoft.com/default.aspx?scid=3Dkb;en-us;321550 - =
"HOWTO:
> Optimize Visual FoxPro Applications While Using Norton AntiVirus 2002"
>=20
> I tend to specify a minimum of 256MB for VFP 8.0 applications and more =
if
> the users are running anything else at the time the app is running.
>=20
> Also check for updates on your printer and/or video drivers - =
especially if
> they aren't using XP explicit drivers.
>=20
> Rick
>=20
> "Mark Kirchner" <markkirchner@lvcm.com> wrote in message
> news:3f60113a$1@tnews.web.dev-archive.com...
> > I'm using VFP 8.0. The systems are Windows XP Pro and have at least =
128MB
> > memory, most more. The majority of the machines are pretty new. The =
error
> > code is C0000005. As far as other software, mostly standard =
Microsoft
> office
> > products along with Norton anti-virus.
> > Mark
> >
> >
> >
> >
> > "Rick Bean" <rgbean@NOSPAMmelange-inc.com> wrote in message
> > news:3f5f5995$1@tnews.web.dev-archive.com...
> > Mark,
> > What kind of "fatal" error are you encountering? C0...05 - These are
> system
> > errors that while VFP can be notified of them, there is no way to =
recover
> > from them, as the OS has already caused the task to die to protect =
itself!
> >
> > There are many causes, including older versions of VFP, printer and =
video
> > drivers, viruses and virus checkers, screen savers, hardware =
(including
> > memory).
> >
> > To start your evaluation, what version and service pack are you =
using?
> (e.g.
> > 5.0 SP3, 6.0 SP5, 7.0 SP1, 8.0) What OSs is this happening on and =
how much
> > memory are they running with? What else is running on the system? =
(e.g.
> > Word, Outlook, Excel, etc.)
> >
> > Rick
> >
> > "Mark Kirchner" <markkirchner@lvcm.com> wrote in message
> > news:3f5f50e5$1@tnews.web.dev-archive.com...
> > > Does anyone have any suggestions on how to track down a fatal =
error? Why
> > > does VFP report a fatal error anyway? I have error trapping and if =
it's
> an
> > > error in my code, why doesn't it get sent to my error trapping =
routine?
> > >
> > > The line of code the fatal error reports is the READ EVENTS in my
> > main.prg.
> > > Main.prg is my "main" startup prg and goes like this:
> > >
> > > * initialization code
> > > do form main
> > > read events
> > >
> > > Then my main form sets up my main buttons and calls all the other =
forms
> > and
> > > prgs.
> > > When it does happen, it seems to be when exiting off one or two
> particular
> > > forms.
> > >
> > > There are about 25 users on the system. The backend is SQL Server. =
I use
> > > remote views and SQL Pass through.
> > > Not all users get the error and it is sporadic.
> > > Usually the users are working for hours before it happens.
> > > However, I am not able to reproduce it here on my test =
environment.
> > >
> > > Could it have anything to do with memory?
> > >
> > > Thanks.
> > >
> > > Mark
> > >
> > >
> >
> >
>=20
>