Your dyslexia is showing, "A bird in the hand is worth two in the bush."
- the bird in the hand has aready been caught.

>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
>
>
>
>>There's Russian saying that could be loosly translated as "There's nothing more permanent than temporary fix". :)
>>
>>>If memory serves, sys(3099) was added in a build after the public beta.
>>>
>>>There's also SET ENGINEBEHAVIOR to do exactly the same thing as sys(3099).
>>>
>>>It's an absolutely valid approach for an existing code base so that the existing code can be examined (and possibly modified) over a reasonable period of time before switching to the 8.0 engine.
>>>
>>>Dan
>>>
>>>
>>>>Yes, it does

SYS(3099, 70)

will switch dataengine to VFP7. However all changes and bug fixes has been and will be applied to VFP8 dataengine only. So it's better to stick with VFP8 mode, if possible.