As far as I know, no DLL conflict should happen in this case. You can get a DLL conflict when you use external DLLs, but VFP is able to handle its own DLLs.

>Hi,
>
>We have not migrated our product to vfp sp2 in order to avoid dll conflicts and confusion in developer machines and at customer sites. However, we are developing a new version of our product that can benefit from Sedna characteristics and want to make the transition now.
>
>I'd welcome advice on the best migration strategy.
>
>Instinct tells me that in order to minimize dll conflicts we should move gradually, keeping old versions in sp1 in case minor correctons become necesary, and only compile new versions of our product with sp2 + sedna. On the other hand, I don't know how to have two versions of vfp in a developer's machine and if this may in fact not be worse than a cold turkey migration.
>
>In case of a cold turkey migration, what changes need to be made in developer machines and what changes on client machines?
>
>TIA,
>
>Alex