How do I use a particular version of a prg? 1

It may not be impossible to combine several versions of web connection, it shouldn't be hard to upgrade all usage to one version. I'd not even try to mix old and new versions.

To still answer your direct question, if files have the same name you're unlucky, within the IDE you can of course address a specific file, but including both a version A and a version B prg, the final EXE will not enable you to distinguish them. So you'd need to start excluding these PRGs to work around that, not a nice perspective.

Using SET PROCEDURE just helps VFP to find PRGs without needing to address the full path, that's not helping you at all, contrary to what you like to achieve it would introduce the problem you have in a final EXE to the IDE environment. Since I know west wind programs use SET PROCEDURE within their code, that's actually something that makes using two different versions harder rather than simpler, even if you yourself address the specifc file in your code, usage of a prg usually does SET PROCEDURE to itself.

So, again, you better upgrade code to make use of the latest versions overall. It shouldn't at all be as much work as you fear it is, because of compatibility.

As an aside, that won't help you: With different DLL versions used by DECLARE DLL you have AS Aliasname with SET CLASSLIB you have AS Aliasname, with SET PROCEDURE you don't have that mechanism for differentiation.

Problems already start if you try to include two PRGs of the same name in two directories. What still works within the IDE then fails to build. VFP clearly doesn't like this kind of parallel usage of different versions of the same libraries and you'd need to cater for it by programming respectively, with version numbers in the class/function/procedure names, for example. I doubt anybody would like a library that instructs you to CLEAR PROGRAMM and/or CLEAR CLASS and/or even CLEAR CLASSLIB after any single call of a function or instantication of a class to let VFP forget what it buffers for usually faster usage, just so that changing to another VCX or PRGR with essentially the same things in older or newer versions does use them instead of what was first used.

Chriss

Thanks Chris, Well your solution is the SMART solution albeit, yes I do dread it. It would be a much better world if I just suck it up and get that done. I'll set down that path. Thanks and have a good day,
John