Exception - Access Violation (0xc0000005)~Dr.Watson

[FoxRookie]

Before my elaboration, 'This site Rocks!' I have solved so many problems with the help of the feedback here.

The sad story begins with one of five customers experiencing a Dr. Watson exception error, Access Violation (0xc0000005) Address: (0x0c00556)

Background: Our application is for mental health providers mostly in VFP 6, but a good portion remains in Fox2.6 that is a customized user configurable interface that is quite impressive, although no users do the configuration (all configuration of this interface has been by "Fairly Well Qualified Programmers" - to include me). This interface running in 'screens' was not successfully converted to 6.0 code and runs in native 2.6. Its really quite awsome.

Our app runs, for this particular customer on NT4 SP6 (not 'a') with Terminal Server and Metaframe. Fiber from server to terminal servers and all servers have 2 gig ram.

Users have a garden variety of computers from Pent100 win95 to current configs.

The scenario: a user will begin data entry on a 'Form' actually fox2.6 screen and open as many as 8 children forms, possibly leaving upto 3 children open while entering multiple instances of a fourth child. After 6 to 10 distal child form saves the Exception Error occurs relatively frequently, but not consistently. However, this can not be duplicated on our companies test bed after hours of data entry (my techs are crazy)

I have read everything on this site, other sites, and have raped the MS Knowledge Base. I am going through our source code line-by-line and there are a few improvements that can be made from the novice code, but nothing stricking.

I am thinking small memory leaks over time with repeated code executions, but can not substantiate.

I am reviewing the Dr. Watson logs but at first this was a bunch of gobily-gook to me-so at re-look I am figuring out what it really means.

I am about NUTS with this and our customer's users are beginning to write bad things about me on bathroom walls in gas stations in their small texas town.

If this rings a bell with anyone, I AM ALL EARS!

THANKS

 

[DEDMOD]

Have you checked how much memory there is on the systems where the problems occur? Or do all systems have the problems sometimes? Dave Dardinger

 

[FoxRookie]

Good Point, I do not know whether the Win95 computers may be running on a deficit --- Good Point

I can't tell you how much i appreciate the imput!

 

[DEDMOD]

Well, one nice thing about checking the configuration of your client's systems is that it makes it look like you're working on the problem and that can be heartening to the client (and your boss) and keep them off you while you figure out the real answer.

Dave Dardinger

 

[DSummZZZ]

One problem with test beds/QA departments is a lot of times they're trying to run the program to death without doing the unpredictable. Jumping to different sections of code or screens or whatever like the end user might do.
However, since they are having a lot of DW errors, they may have corrupted tables and indexes. Have you rebuilt the indexes from scratch at their location? Not by using REINDEX but by deleting the index file(s) and rebuilding them. Bad indexes and headres cause a lot of GPFs.

Dave S.

 

[Nro]

Allo

I know how you feel. If you have not already jump out a window, you can try this ;

1 - Try to delete the FOXUSER.DBF and FPT (if you use it)
2 - Try to recreate all the indexes from scratch
3 - Always compile your .EXE on an Windows '95 machine
4 - Patch your Fox 2.6 to Fox 2.6a (I'm sure you did)
5 - Call Bill Gates and give him all your ... well, it's not a good idea.
6 - Pack the files et pack the Memo
7 - Recreate the whole Database structures

use table1
copy to pipo structure extended

select 0
use pipo
append from table1

.
.
.

8 - The last thing to do, is to definitively convert your apps into VFP 6.0 or VFP 7.0. BTW, you can hack the converter program (convert.prg) and change it for your needs (we convert systems with more than hundred screens)

Hope this give you some id.

Good luck (sorry, you don't need luck, you need GOD intervention)

Nro