MartyConnelly
martyconnelly at shaw.ca
Fri Mar 21 15:10:00 CST 2003
I am guessing (don't know how you are installing mda) but there is a difference in how Access 97 and 2000 (+ )resolves references. ACC97: How Access 97 Resolves Visual Basic for Applications References (Q280465) ACC2000: How Access 2000 Resolves Visual Basic for Applications References (Q248941) ACC2002: How Access 2002 Resolves Visual Basic for Applications References (Q286300) The latter two have an extra step for resolution and also look in different directories. Also MS has added in Office 2000 a method of adding an Office COM Addin that will link to all office products at same time; maybe this is causing the reference checking problem. Sort of an MDA for Word, Excel and Access. At some point Access has to resolve for these as well. HOWTO: Build an Office 2000 COM Add-In in Visual Basic Q238228 --------------------------------------- Have a look at Tony Toew's site for his notes on using Addin's especially if using MDE's http://www.granite.ab.ca/access/addins.htm ---------------------------------------- Here is Dev Ashish's method for late binding a mapi session where mobjSession set to object Public Sub MAPILogon() On Error GoTo err_sMAPILogon Const cERROR_USERCANCEL = -2147221229 mstStatus = SysCmd(acSysCmdSetStatus, "Login....") Set mobjSession = CreateObject("MAPI.Session") mobjSession.Logon exit_sMAPILogon: Exit Sub err_sMAPILogon: mboolErr = True If Err = CdoE_LOGON_FAILED - mcERR_DECIMAL Then MsgBox "Logon Failed", vbCritical + vbOKOnly, "Error" ElseIf Err = cERROR_USERCANCEL Then MsgBox "Aborting since you pressed cancel.", _ vbOKOnly + vbInformation, "Operatoin Cancelled!" Else MsgBox "Error number " & Err - mcERR_DECIMAL & " description. " _ & Error$(Err) End If Resume exit_sMAPILogon End Sub Charlotte Foust wrote: >Thanks, but I found all thatwhen we were first researching putting this >in to a library in the first place. Right now I'm trying late binding >in the library database to see if we can at least get it to bomb >gracefully instead of breaking the application that references it. The >problem is that in A97, the breakage was limited to the library database >and the application database just realized that it couldn't use email. >In AXP, the breakage affects the application database, not just the >library. > >Charlotte Foust > >-----Original Message----- >From: MartyConnelly [mailto:martyconnelly at shaw.ca] >Sent: Thursday, March 20, 2003 5:24 PM >To: accessd at databaseadvisors.com >Subject: Re: [AccessD] Access XP and references in libraries > > >CDO is a wrapper around MAPI, the license is not redistributable but the > >version (1.1, 1.2, 1.21 and ver 6.0) you have depends on what you have >installed from a selection of Exchange, Outlook and WinXP or win2000. > >By default, Outlook 2000 and Outlook 2002 installations do not include >the CDO 1.2x component. When you view the options for Office or Outlook >setup, CDO is listed under the options for Outlook. > > For a full table of versions and what installs see INFO: Where to >Acquire the CDO Libraries (all versions) >http://support.microsoft.com/default.aspx?scid=kb;EN-US;171440 > >For more info see: >http://www.cdolive.com/start.htm > > >Charlotte Foust wrote: > > > >>In 97, we had used a library database that had a reference set to the >>CDO.DLL library so we could handle email features using Redemption. >>If that DLL was missing on the target machine, the library had a >>broken reference but it didn't affect the main project except that the >> >> > > > >>email capabilities were disabled. In XP, when you load the app, you >>get a message that the CDO.DLL is missing. I assume the difference in >> >> > > > >>behavior is because of the change in the VBE IDE in 2000 and later, >>but does anyone know what the further implications might be? We >>haven't deployed this app yet, so I'm looking for input. >> >>Charlotte Foust >> >> >> > > >_______________________________________________ >AccessD mailing list >AccessD at databaseadvisors.com >http://databaseadvisors.com/mailman/listinfo/accessd >Website: http://www.databaseadvisors.com >_______________________________________________ >AccessD mailing list >AccessD at databaseadvisors.com >http://databaseadvisors.com/mailman/listinfo/accessd >Website: http://www.databaseadvisors.com > > >