>Armin,
>
>>I'm currently looking around in the MM data access classes (cCursor, etc.) to find the difference between two properties: CursorSource and cCursorSource. Before I go into this too deep in code, I thought, that someone might be able to tell me.
>
>"ccursorsource" is the primary place you should look for the true cursor source of the data access object. CursorSource was used in previous versions of the Framework but (based on the Framework version being used) does not always contain the cursor source.
>
>Regards,


Kevin,

VCXEdit is still showing that the 'LocalTablesEnvironment' is using 'CursorSource' and I'm using V6.1.2. I notice that new environments have the view alias in 'cCursorSource' and the view name in 'CursorSource.' My older environments have the same except that the brackets show up around the view name in 'CursorSource.'

I also wrote about the phenomena of opening the LocalTablesEnvironment class, saving it without making any changes, closing it then reopening it and find that 'CursorSource' for every table in that class has been changed to "..\h.dbf.' The pathing of "..\h.dbf' changed slightly depending on my current default folder, too. All this is outside of the framework which led me to think that 'Cursorsource' is a VFP reserved word. This quirk is also the reason that one has to delete a table then re-add it to it's environment class if one edits it thru the builder. Why this quirk only affects edited info as opposed to added info is a study all by itself.

James Weil 2 years ago sent in a fix for the famous problem of the "[" and "]" surrounding the table/cursor name in the 'CursorSource' property. After editing the LocalTablesEnvironment, some see the listbox in the data utility for packing and reindexing display the tables names preceded and suffixed with underscores, which is the way the Listbox displays brackets. Again, the source of the info appearing in the list box is the 'CursorSource' property.

Ahh... the joys of computing...