I have been doing VFP since VFP came out. The length of my experience in not relevant, but that fact that in
all these years of publishing VFP applications I have never come across this means that the behavior is avoidable.

Well, we have that in common. I've been working with Fox since FoxBase 1.02 and then VFP since VFP 3.0. :) So let's keep this friendly.

Of course. Can't you see me grinning from ear to ear? :)



And that IS relevant. The framework is setting up an environment which is causing or allowing it to happen.

Well, I don't see it that way, exactly. For example. If you don't code with m. on your variables, whose fault is it when a=a+1 crashes because there's a character field in the table called a? The situation exists whether we've been bitten by it or not.

I never use the 'm.' style, and I've never had it be a problem, although I understand what you're saying.

But look at it this way - if I wrote applications all the time that don't exibit that behavior, then I
inherit an app that IS showing that behavior, it's something in that app, not generalized VFP behavior.


I have never had to do what you're doing below and would rather help you not have to do some kind of workaround. What do you think?

You've never opened a form with DO FORM??

I am all ears when you speak, so feel frere to post any and all suggestions.