Alastair,
Another 'hidden' place to check is forms. It is
possible to create a variable such as VNumber INTEGER and
place the variable on a form. Later you determine you would
rather change the variable type to TEXT. You change the
variable in all your code. Everything is fine until the
form opens and the form re-types the variable back to
INTEGER, as it was when the variable was placed on the form.
In order to have the variable typed properly, you
have to delete the variable. Then put the variable back on
the form while it is the correct type.
I can't remember whether columns automatically
change on a form to the new data type, or whether this
process must also be used for columns after changing data
type.
Once I started clearing, and pre-defining all form
variables to null or whatever in the code just prior to
opening a form I stopped having these kind of crashes.
Randy Peterson
PS. Using TRACE should show you the specific command which
is not being interpreted successfully. You can use that
same command from the R:Prompt, or check the values of
variables and system settings to continue to approach the
cause of the difficulty.
I religiously use R:Code.
----- Original Message -----
From: "Alastair Burr" <[EMAIL PROTECTED]>
To: "RBASE-L Mailing List" <[EMAIL PROTECTED]>
Sent: Sunday, December 29, 2002 6:52 PM
Subject: [RBASE-L] - Criteria For My Unstableness With
R:Base6.5++ Build 1.862
> Just to be absolutely sure that my code has no obvious
errors I have run
> every command file and eep through RCode today - after the
crashes mentioned
> below.
>
