David,

Make a backup of your scx/sct first.

The cursor rows in the CSX will be at the top of the table. You should be able to open the properties memo in a browse window to isolate the correct row and delete it. This should let your form open in the designer.

You might also temporarily recreste a view with that name, edit the form, remove the view from the DE, them delete the view from the DBC.

>I have a form that is giving me the error
>'Error instantiating cursor object', upon load of the form in design time or at run time. The reference is to a view that no longer exists. However, if i ignore the error, then, when I go into the form in design mode, I can not find the cursor object to delete it, which is what I want to do, since I don't need it anymore.
>
>If I open the scx as a table, I still see a reference in the scx to the cursor object.
>
>Then, in order to try to understand this behaviour I tried the following:
>
>1) create a test form t1
>add a view to the data environment save the form - exit
>2) drop the view
>3) try to modify the form again
>4) I get the error instantiating cursor object error. I hit ignore. I can't find the reference to the cursor object in the de.
>5) I opened t1.scx as a table.
>6) I deleted the record for the cursor object
>7) I tried opening the form again in design mode - foxpro blows up and gives me 'error referencing memory' error - and then quits
>8) I then went into the t1.scx table again, and this time i deleted the DE record.
>9) then I opened the form again - and it worked - vfp seemed to recreate the DE?
>
>
>What is the proper/safe procedure here - if one deletes an object that the de references - prior to deleting the object from de itself - and then one goes into the form again in design mode?
>
>I'd like to just do what I did on my t1 test form, for my production form, but it seems like it might be dangerous.