Re: managing References
- From: "Alex Dybenko" <alexdyb@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Sat, 22 Oct 2005 18:54:47 +0400
Hi,
yes, ADOX is bit tricky, you should use exact version number you installed.
so you either have to install same ADO version on all PCs, or use late
bindings (declare ADOX variables as objects and remove reference)
--
Alex Dybenko (MVP)
http://alexdyb.blogspot.com
http://www.PointLtd.com
"rocco" <rocco@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:8E60EBEA-7330-4A36-B961-9247B71856A9@xxxxxxxxxxxxxxxx
> Hello,
> I'm developing a databse on a pc running Office 2003. I have Visual
> Studio.NET 2003 and MDAC 2.8 installed on this system.
> Since I need the db to run on a pc that has only Office 2000, I have
> referenced:
> - Microsoft Access 9.0 Object Library (instead of 11.0)
> - Microsoft ActiveX Data Objects 2.1
> Since I need to use also ADOX in my code, I have to reference to the
> msadox.dll.
> But on my system I can only find:
> - Microsoft ADO Ext. 2.7 for DDl and Security.
>
> Once I updated to MDAC 2.8 I cannot find a 2.1 for this library.
> Will it work anyway?
>
> And... Why I see on my system Microsoft ADO Ext. 2.7 for DDl and Security
> instead of Microsoft ADO Ext. 2.8 for DDl and Security??
>
> I know I can suggest to upgrade the pc with MDAC 2.8 and i can give them
> the
> redistributable package for that, but I prefer to deliver only the
> database
> and nothing more.
>
> thanks,
> Nico
.
- Prev by Date: Re: set value of object
- Next by Date: ===>Delete record(s)/record set based on a criteria
- Previous by thread: Re: set value of object
- Next by thread: ===>Delete record(s)/record set based on a criteria
- Index(es):
Relevant Pages
|