Yep, and since this a 'default' name via VFP ( not mine or MM ) 'blame' MicroSoft.

FYI Here are some notes I just wrote up for an internal How to work with MM doc I am creating:

What should be done to fix this?

A: The Data Access object that the Biz Obj uses has a property named CursorSource. This is an unfortunate name because it is a reserve word used by the Cursor Class, and VFP has some trouble with it. In this case one should not attempt to change the information in the property at design time, e.g. via the property sheet because as soon as the Biz Object is saved the property will be given a value something like …. h.dbf. Three possible fixes:

1) Start Over ( ‘Best solution’ )
Make sure to extract any Biz Specific code into some Temp file. Delete the Data Environment class(es) and the Biz Object. ( Yes for unknown reasons delete the Biz Object also. Well maybe for a first attempt try it w/o deleting the Biz Obj. ) Reconstruct the classes using code saved.

2) Alter the Init of the Data Access Object
Add code like this to the Data Env Object’s INIT Method ( This code is untested but the concept was used and it did work )
This.CursorSource = This.cCursorSource
Return DoDefault(
Make sure the cCursorSource has the proper Table/View etc. value

3) Change the property via runtime code.
This suggestion is just theory, but it may be possible to create a ‘jig’ program to instantiate the data environment, alter the CursorSource property value and save the class.