>>>>Will having both the latest 6.0 and 7.0 builds on the same computer inadvertantly introduce any DLLs or other 'behind the scenes' files into the 6.0 stuff?
>>>
>>>Nope. I've got 5.0, 6.0 and 7.0 living quite happily together on a couple of machines.
>>
>>Mike,
>>
>>THanks. Before I loaded it on my machine at work I thought I'd check once more.. <g>
>
>Frankly, I think the question is what happens if you build an executable on a machine where 7 is installed - do any of the novelties at the system level get included behind our backs? Imagine this scenario - I'm shipping an executable to a client, to install on a machine where I already have another VFP6 exe, and this new exe is also v6, but built on a machine where all the system components were upgraded in order to have VS.NET installed. Now will the old exe be guaranteed to perform?
Dragan,
You've nailed it with respect to my concerns. I just want to be 100% sure I don't inadvertantly get 7.0 components in what should be a 100% 6.0 build.
Thanks...
Best,
DD
A man is no fool who gives up that which he cannot keep for that which he cannot lose.
Everything I don't understand must be easy!
The difficulty of any task is measured by the capacity of the agent performing the work.