>That's bizarre -- I know for a fact that they had fixed this at one time in the VFP 6 beta because I was the one who reported it originally and removed it from my "outstanding bug" list once I'd found they'd fixed it. It must've gotten broken again. Maybe they should use SourceSafe to track these things <g>.
>

Well, I have a little bit of egg on my face. I think you are right, the bug has been fixed.

Where I went wrong was assuming that the fault was that VFP would "corrupt" the view when the DBSETPROP() command was issued. So when I was testing, I would set the property, and then try to open the view. Well, I was opening the view with a tool that was compiled in VFP 5, and The error was surfacing. So I assumed VFP 6 was responsible. But it turns out that the fault is with the version hat opens the view. The error does not surface ever when the view is opened in VFP6.

I sure confused the heck out of the poor support guy at MS though- he apparently was suffering from the same confusion as I, and saw it sufficient to resubmit the bug to the Fox team. I wrote back to let him know when I figured out what was going on.

I still won't be putting back the ability to edit this property into eView, I am trying to keep it compatible with VFP 5.