[AccessD] Access Check References

Hi William

I guess not as is, but if you modify/simplify it to not remove and add back a reference - so a recompile is not needed - it should.

/gustav


>>> wdhindman at dejpolsystems.com 27-05-2009 13:24 >>>
...will any of this work in a runtime mde install?

William

--------------------------------------------------
From: "Gustav Brock" <Gustav at cactus.dk>
Sent: Wednesday, May 27, 2009 6:06 AM
To: <accessd at databaseadvisors.com>
Subject: Re: [AccessD] Access Check References

> Hi William
>
> Here it is:
>
> http://databaseadvisors.com/pipermail/accessd/2003-July/011034.html 
>
> /gustav
>
>
>>>> wdhindman at dejpolsystems.com 27-05-2009 11:41 >>>
> Gustav
>
> ...I understand  the references from the standpoint of using them from
> Tools/References toolbar as I've normally used them before ...this is the
> first time I've used vba code to check them.
>
> ...as I noted in my reply to Stu, its the major and minor numbers that are
> confusing to me ...ie, Access 9.0 "should" be Access 11.0 ...or maybe not.
>
> ...any insight/links/suggestions would be appreciated ...I'm using the
> current slowdown to rebuild my template app from scratch, trying to 
> correct
> a lot of accumulated garbage from the past ten years with some highly
> distilled "best practices" ...anything that would verify the references at
> startup would appear to fit that mold ...tks.
>
> William
>
> --------------------------------------------------
> From: "Gustav Brock" <Gustav at cactus.dk>
> Sent: Wednesday, May 27, 2009 3:30 AM
> To: <accessd at databaseadvisors.com>
> Subject: Re: [AccessD] Access Check References
>
>> Hi William
>>
>> Go to Tools, References and note that the top two can't me unmarked -
>> native to ("built in") Access, can't be removed.
>> The OLE reference may often be deselected.
>> The remaining two, DAO, ADODB, you probably use in your code. If you 
>> don't
>> know, unmark each and compile and you will see.
>>
>> You may expand your code a bit:
>>
>>   For Each chkref In Application.References
>>        strLog = strLog & IIf(chkref.IsBroken, "## Broken Reference ", "OK
>> ") & chkref.BuiltIn & " ref: " & chkref.Name _
>>               & " " & chkref.Major & "." & chkref.Minor & " " &
>> chkref.FullPath & vbNewLine
>>    Next
>>
>> Note too, that this only lists the references, it doesn't actually verify
>> them. How to do this has been discussed several times - I can find links
>> should you wish that.
>>
>> /gustav
>>
>>
>>>>> wdhindman at dejpolsystems.com 27-05-2009 07:58 >>>
>> 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?
>>
>> William