[AccessD] Access Check References

William Hindman wdhindman at dejpolsystems.com
Wed May 27 06:29:36 CDT 2009


...I'm heading off to get some sleep but I 'thimk" that I have to somehow 
ask it for the max version, not the base which I think is what we're seeing 
...but then again I need sleep badly ...when I was 25 I could work 72 hrs 
w/o a nap and still be effective ...at 62 my body rebels after less than 24 
w/o some sleep ...and its just plain old shutting down as I type :(

William

--------------------------------------------------
From: "Stuart McLachlan" <stuart at lexacorp.com.pg>
Sent: Wednesday, May 27, 2009 6:49 AM
To: "Access Developers discussion and problem solving" 
<accessd at databaseadvisors.com>
Subject: Re: [AccessD] Access Check References

> Good question!
>
> I get the same strange version numbers and you are correct, they are not 
> the right Versions
> according to everything I can find.  I've no idea where they come from and 
> I can't find
> anything on the web to explain it.
>
> WTF?  MS DLL Hell strikes again?
>
>
> On 27 May 2009 at 5:30, William Hindman wrote:
>
>> ...duh ...good question ..."I" think its as follows:
>>
>> VBA 4.0 ...should be VBA 6.0
>> Access 9.0 ...should be access 11.0
>> DAO 5.0 ...should be DAO 3.6
>>
>> ...but maybe NOT ...I've never actually looked at the references this way
>> before.
>> ...so tell me,  what is correct and where can I find any "reference" to
>> those reference numbers, eh
>> ...I'm more than a bit confused, apparently a result of getting old ...or 
>> so
>> I'm told by the kids.
>>
>> William
>>
>> --------------------------------------------------
>> From: "Stuart McLachlan" <stuart at lexacorp.com.pg>
>> Sent: Wednesday, May 27, 2009 3:29 AM
>> To: "Access Developers discussion and problem solving"
>> <accessd at databaseadvisors.com>
>> Subject: Re: [AccessD] Access Check References
>>
>> > Looks to me like:
>> >
>> > Name   Major Minor  FullPath
>> > VBA        4       0       C:\Program Files\Common Files\Microsoft
>> >                                       Shared\VBA\VBA6\VBE6.DLL
>> > Access     9      0      C:\Program Files\Microsoft
>> > Office\OFFICE11\MSACC.OLB
>> > DAO         5      0      C:\Progra~1\Common~1\Micros~1\dao\dao360.dll
>> > etc.
>> >
>> > What's the problem?
>> >
>> >
>> > On 27 May 2009 at 1:58, William Hindman wrote:
>> >
>> >> Group
>> >>
>> >> ...I'm running the following code within a private sub in my startup
>> >> form:
>> >>
>> >>     Dim chkref As Reference
>> >>
>> >>     For Each chkref In Application.References
>> >>         strLog = strLog & IIf(chkref.IsBroken, "## Broken Reference",
>> >> "OK")
>> >> & " ref: " & chkref.Name _
>> >>                & " " & chkref.Major & "." & chkref.Minor & " " &
>> >> chkref.FullPath & vbNewLine
>> >>     Next
>> >>
>> >> ...works like a charm ...except that the log reads as follows:
>> >>
>> >> OK ref: VBA 4.0 C:\Program Files\Common Files\Microsoft
>> >> Shared\VBA\VBA6\VBE6.DLL
>> >> OK ref: Access 9.0 C:\Program Files\Microsoft 
>> >> Office\OFFICE11\MSACC.OLB
>> >> OK ref: DAO 5.0 C:\Progra~1\Common~1\Micros~1\dao\dao360.dll
>> >> OK ref: stdole 2.0 C:\WINDOWS\system32\stdole2.tlb
>> >> OK ref: ADODB 2.8 C:\Program Files\Common Files\System\ado\msado15.dll
>> >>
>> >> ...where the heck did the VBA 4.0/Access 9.0/DAO 5.0 come from?
>> >>
>
> -- 
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
> 





More information about the AccessD mailing list