record is out of range

FWIW, I got this error when trying to save a form I was working on in VFP9.
The form was pretty new, no code in it yet, just a lot of controls. I tried
to recover by creating a new form of the same class and copying and pasting
the controls onto the new form. It seemed to work at first, but on the
second attempt to save, I got "File is not open". I then pasted the controls
onto a new base class form and saved it. Then FoxPro crashed. On restart,
the second rescue form seems to be OK.

I don't know if this means anything to anyone, but I thought I'd mention it.

--
You can reach me at: p one six seven (remove spaces and convert words to
digits) at comcast dot net

Steve
Fri Oct 14 17:39:25 CDT 2005

Paul,
I've had the same occasional problem over the years with different
versions of Foxpro and different computers. I can only conclude it's a
built-in "anomaly" which no one knows how to fix. In a way I'm glad to
see someone else has experienced this (some consolation, huh?)

My workaround is to try to save more frequently, or before I've spent
a lot of time creating the form.

BTW with VFP9, I've experienced my report builder closing on me at
unexpected times, losing all changes I've made up to that point. I've
forced myself to save more frequently, figuring it's the same type
problem as above.

Just ranting, sorry, no solution :)

Steve Meyerson



On Wed, 12 Oct 2005 18:05:35 -0700, "Paul Pedersen"
<no-reply@swen.com> wrote:

>FWIW, I got this error when trying to save a form I was working on in VFP9.
>The form was pretty new, no code in it yet, just a lot of controls. I tried
>to recover by creating a new form of the same class and copying and pasting
>the controls onto the new form. It seemed to work at first, but on the
>second attempt to save, I got "File is not open". I then pasted the controls
>onto a new base class form and saved it. Then FoxPro crashed. On restart,
>the second rescue form seems to be OK.
>
>I don't know if this means anything to anyone, but I thought I'd mention it.