|
Home > Archive > Getting Started with dBASE > July 2005 > dbase codes
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]
|
|
|
| Sometimes when I am trying to open or close a form from the design menu or
open a form into the source editor from design menu. I get this error:
"dbase plus has encountered an internal or operating system error. Do you
want to save any unfinished work before exiting? Choose Yes to continue
working in dbase plus, it is recommended that you exit immediately after
saving any unfinished work. Choose No to exit no"
Then dbase hangs up for a few seconds then it closes.
I am using windows xp professional, but I have had this error messsage on
windows 2000 and windows 98.
| |
| Todd Kreuter 2005-07-13, 7:23 am |
| Will wrote:
>
> Sometimes when I am trying to open or close a form from the design menu or
> open a form into the source editor from design menu. I get this error:
>
> "dbase plus has encountered an internal or operating system error. Do you
> want to save any unfinished work before exiting? Choose Yes to continue
> working in dbase plus, it is recommended that you exit immediately after
> saving any unfinished work. Choose No to exit no"
>
> Then dbase hangs up for a few seconds then it closes.
>
> I am using windows xp professional, but I have had this error messsage on
> windows 2000 and windows 98.
What version of dBASE? This use to be fairly common in the early days of
7.x. While it has been cleaned up, it has not been completely wiped out.
My guess is that something on your form is the cause, perhaps a circular
reference, a forced release(), an invalid try/catch/endtry, etc.
--
Todd Kreuter [dBVIPS]
| |
|
| I am using dbase plus 2.21, can you elaborate more on the possible causes
"Todd Kreuter" <tkreuter@dbvips.usa> wrote in message
news:42D50ADF.4291BDB8@dbvips.usa...
> Will wrote:
>
> What version of dBASE? This use to be fairly common in the early days of
> 7.x. While it has been cleaned up, it has not been completely wiped out.
> My guess is that something on your form is the cause, perhaps a circular
> reference, a forced release(), an invalid try/catch/endtry, etc.
>
> --
> Todd Kreuter [dBVIPS]
| |
| Todd Kreuter 2005-07-13, 9:23 am |
|
Will wrote:
>
> I am using dbase plus 2.21, can you elaborate more on the possible causes
It would really take a trained eye to see where the problem might be.
Is this happening on one or more forms? Are you using dataModRef's? Do
you manually create any references to the form? Do you use
try/catch/endtry? Do you use release()?
When you open and close the form, use ? findInstance("FormClassName") to
see if an instance of the form remains in memory. If that returns
"Object", then the form is still in memory when it likely should not be
(note you need to replace "FormClassName" with the class name of the
form you want to check).
--
Todd Kreuter [dBVIPS]
|
|
|
|
|