you can.<BR><BR>He's not setting up his project with binary compatability, me thinks. <BR><BR>As for which component it's actually calling is anybody's guess. You don't know which GUID it's referring to anymore.
You can determine which version of a COM component will be instantiated when multiple versions of the library are installed on the same computer.<BR><BR>But you can also control explicitly which version is created. To do so, just use the complete version-dependent ProgID in your CreateObject statement, like this:<BR><BR>Dim adoCn<BR>Set adoCn = CreateObject("ADODB.Connection.2.7")<BR><BR>You can see all the available version-dependent ProgID's by looking in the system registry. There will be a key called ADODB.Connection (or whichever COM object you're creating) directly under the HKEY_CLASSES_ROOT hive of the registry. Right under this key, you'll see other keys, representing all the available versions on the computer, like this:<BR><BR>ADODB.Connection<BR>ADODB.Connection. 1<BR>ADODB.Connection.2.1<BR>ADODB.Connection.2.5< BR>ADODB.Connection.2.6<BR>ADODB.Connection.2.7<BR ><BR>That should help you with creating late-binded instances of a COM object.<BR><BR>Reginald Dawson