Hi Dan,

I'm not against using SET ENGINEBEHAVIOR TO 70 "for the right reasons". I have no doubt that you'll use it responsibly. :).
I'm trying to point out consequences of using it as a permanent fix.

>Yes, and there's a US saying that "Two birds in the hand are better than one in the bush".
>
>In our case, we're sitting on a heap of code written in VFP6. We can stay in VFP6 or move forward. SET ENGINEBEHAVIOR lets us run unchanged in VFP8 until we decide to revisit old code.
>
>We have code that does not work with SET ENGINEBEHAVIOR 80. It needs to be rewriteen and we know it. But we also know that implementing other new features will render that code obsolete. Rather than editing the code, we can just delete it after implementing new features. Until then, the old code must run as is.
>
>There's no reason not to use SET ENGINEBEHAVIOR, when used for the right reasons.
>
>Dan