Yes, that would work if the old app depended on EngineBehavior=80 and you had control of the source code for the new app. But if the new app was also a 3rd party app from an independent vendor (no source code) and it required EngineBehavior=90, then you're still stuck.

I think that what MSFT should have done was require developers to explicitly issue EngineBehavior=90 (as a SET command via Connection.Execute) if that's what was wanted from this newer DLL, otherwise it should by default operate with EngineBehavior=80.

>> but that solution assumes you have the source code for all apps in use.
>>
>
>Hi Mark,
>
>You don't need to have the source code. Just put
>

>EngineBehavior = 80
>

>into CONFIG.FPW next to VFPOLEDB.DLL.
>
>Aleksey.