Re: Late Binding

Microsoft ActiveX Data Objects 2.7 Library is the reference for ADO, an
alternate means of interacting with the data.

You can try unchecking the reference, and then compiling your application
(under the Debug menu while in the VB Editor). If you're not using ADO, the
application should compile properly. If it doesn't compile, it may mean you
need to add the Microsoft ActiveX Data Objects 2.7 Library reference back.
(Not being able to compile, though, could be due to some other error, not
the fact that you're using ADO)

--
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no private e-mails, please)


"tmort" <tmort@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:0A1A6C51-52A7-40DC-9C35-3DBA9799D345@xxxxxxxxxxxxxxxx
Thanks,

What about the AciveX reference?

Since I took out the code that deals with using the ActiveX email client I
am not aware that I am using any ActiveX.

I still have the smtp ActiveX client registered with Windows.

Any ideas

"Douglas J. Steele" wrote:

DAO 3.6 is the correct reference for Access 2000, Access 2002, Access
2003
and Access 2007 (when not converting to the Access 2007 ACCDB file
format)

--
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no private e-mails, please)


"tmort" <tmort@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:DDA48267-ADBE-4D03-9F53-41BA9DD5971F@xxxxxxxxxxxxxxxx
So are you saying that DAO is not version specific and 3.6 will work
with
older installation?

"tmort" wrote:

I have an Access db developed with Access 2003 that will work (with
adjustments to references) with 2002 and 2000. Presumeably it will
also
work
with Ofice 2007.

So far I've manually adjusted references for each machine I install it
on.
I'm told that I should look into late binding. I've found some
discussions
on how to do this with Excel and Outlook. It looks like I change the
way
I
call thse by changing as object to application or vice versa where I
call
them.


I'm pretty sure that I've had to change some of the other references
as
well
and I don't know if I can use late bindings with the others or how.


The references I use are:

Visual Basic for Applications
Microsoft Access 11.0 Object Library
Microsoft DAO 2.5/3.51 Compatibility Library
OLE Automation
Microsoft ActiveX Data Objects 2.7 Library
Microsoft Excel 11.0 Object Library
Microsoft Outlook 11.0 Object Library

Can someone help me with this? I saw another post that says to look
at
the
MVP site, but, I haven't been able to locate it.

Thanks






.

Relevant Pages

  • Re: Access 2003-Access 2002 Incompatibility
    ... Microsoft ActiveX Data Objects Recordset 2.7 Library ... The first one corresponds to msado15.dll (and adds the ADODB reference), ... There are two ADO type libraries. ...
    (microsoft.public.access.conversion)
  • Re: NTSVC.OCX Help needed
    ... The only things reference in the application beyond the standard ... > VB references are NTSVC.OCX, Microsoft ActiveX Data Objects 2.5 Library, ... I believe Desaware made a commercial service control. ...
    (microsoft.public.vb.general.discussion)
  • Re: Compile Error - ADODB.Recordset Error "User-defined type not defined"
    ... using ADODB required a reference to the ... Microsoft ActiveX Data Object 2.x Library. ... Dim rst As ADODB.Recordset ... one I should check as there are 9 variations of "Microsoft ActiveX Data ...
    (microsoft.public.access.modulesdaovba)
  • Re: Missing reference library
    ... By not checking the reference ... Microsoft ActiveX Data Objects 2.5 and this worked fine. ... Animation Carbon: Copy/Paste/Share animation libraries. ...
    (microsoft.public.powerpoint)
  • Re: email data from form
    ... Requires that your references include Microsoft CDO for Windows 2000 Library ... ' Reference to Microsoft ActiveX Data Objects 2.5 Library ...
    (microsoft.public.access.formscoding)