Referencing at design time

A general problem in VB I have not figured out is that you must REFERENCE
the COM objects at desing time. If you reference ADO versions older or newer
than the machine that will run your program, it won't work. I surely am
mistaken, because components get updated to newer versions all the time, and
if your software quits working every time a dll is updated, it would be
unusuable!

Lisa

Always develop on a machine that has the oldest installation you will
need to support. Reference the oldest available DLL and don't be
version specific when you instantiate things. For example, if
instantiating something for DAO don't reference "DAO.36" or "DAO.35"
just use "DAO".

--
Ken Slovak
[MVP - Outlook]
http://www.slovaktech.com
Lead Author, Professional Outlook 2000 Programming, Wrox Press
Lead Author, Beginning VB 6 Application Development, Wrox Press
Attachment Options
http://www.slovaktech.com/attachmentoptions.htm
Extended Reminders
http://www.slovaktech.com/extendedreminders.htm


"Lisa Pearlson" <no@spam.pls> wrote in message
news:O$CUllLQDHA.452@TK2MSFTNGP11.phx.gbl...
> A general problem in VB I have not figured out is that you must
REFERENCE
> the COM objects at desing time. If you reference ADO versions older
or newer
> than the machine that will run your program, it won't work. I surely
am
> mistaken, because components get updated to newer versions all the
time, and
> if your software quits working every time a dll is updated, it would
be
> unusuable!
>
> Lisa
>
>