[AccessD] Calling ADO without having to roll out fivehundrednewmdbs

..afaicr if you reference an older version than installed, the newer 
version will be used without any user interaction ...but if you reference a 
newer version than the one installed and use new or revised calls that are 
differentiated between the two versions you will get a compile error on a 
missing reference.

William Hindman


----- Original Message ----- 
From: "Gustav Brock" <Gustav at cactus.dk>
To: <accessd at databaseadvisors.com>
Sent: Thursday, January 20, 2005 8:42 AM
Subject: Re: [AccessD] Calling ADO without having to roll out 
fivehundrednewmdbs


> Hi Mark
>
> Typically a newer version will be accepted while and older will not.
> But only testing can determine this for sure.
>
> /gustav
>
>>>> marklbreen at gmail.com 20-01-2005 14:09:22 >>>
>
> My next concern (and I am not asking for help, just thinking out load)
> is the versions of ADO that we will reference.  What happens if I
> reference ADO version 2.6 for example, but the user has a later or
> earlier version than the development machine?
>
> Do I need to programatically enumerate the references and check for
> "missing" and then programatically attempt to assign another version
> of ADO?  Does not sound that pretty !
>
> I am not too concerned about needing the latest version, all we are
> doing is calling an Oracle stored procedure and accepting output
> parameters (hence the need to ADO in the first place).
>
> -- 
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>