|
Home > Archive > Programming with dBASE > June 2005 > error message
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
|
|
| Rick Gearardo 2005-06-22, 1:23 pm |
| Does anyone know what the following means:
Internal error:class 1 Internal error. Please contact dBase,Inc; 1
TIA,
Rick
| |
| *Lysander* 2005-06-23, 3:23 am |
| In article <nL$Tkc1dFHA.432@news-server>, dbase@NO_SPAMsecurit
ycorp.com=20
says...
> Internal error:class 1 Internal error. Please contact dBase,Inc; 1
This is plusrun.exe telling to you and it basically means:
"I am choking on some part of your code, go fix it!"
or maybe
"Maaaaami! Someone is occupying _MY_ part of RAM"
seriously,
this error message usually points to losses in memory or to memory-
access violations. You would be lucky to find the source.
Start searching by isolating the lines of code which are _usually_=20
producing this code.
If there is no such special place, look for all possibly left-open=20
references to objects that are not existing anymore, or for objects=20
belonging to parents, where the parents are not existing anymore.
--=20
ciao,
Andr=E9
~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~
Deutsche dBase-Konferenz dBKon 2005 ::: 11. bis 13. November 2005
Deutschsprachige Konferenz zu dBase und anderen Datenbanken
Info: www.dbase-konferenz.de
| |
| Rick Gearardo 2005-06-23, 7:23 am |
| It's in an app that's been running for 2.5 years so I don't think it's the
code. The error comes when changing the value of a datalinked checkbox. I've
been having some file corruption problems which I hope had been cleaned up.
I also turned of f Oplocks on all the clients.
I had made a change to the .wfm file, added an if...endif to check for a
form.property value around an existing function that has nothing to do with
the checkbox or the datalinked field. When I copied the old .wfo back it
worked again. This is maybe pointing to some problem copying to the network.
Rick
This is plusrun.exe telling to you and it basically means:
"I am choking on some part of your code, go fix it!"
or maybe
"Maaaaami! Someone is occupying _MY_ part of RAM"
seriously,
this error message usually points to losses in memory or to memory-
access violations. You would be lucky to find the source.
Start searching by isolating the lines of code which are _usually_
producing this code.
If there is no such special place, look for all possibly left-open
references to objects that are not existing anymore, or for objects
belonging to parents, where the parents are not existing anymore.
|
|
|
|
|