Hi, Aaron.
either that, or macro security is set = high?
At least we can rule out that possibility, since Tracy complained about the
inability to compile the code and mentioned that the error message stated
"Library not found." Tracy would experience none of these behaviors if the
macro security level were set to high for Access, because Access would
refuse to even open the "untrusted" database file. When attempting to open
the database Tracy would receive the error message, "Security settings
restrict access to the file because it is not digitally signed." Tracy did
not complain that the database wouldn't open, nor that a security message
warned that it couldn't be opened.
Even if Tracy's database were "trusted," the database file would open, but
merely setting the macro security level at high would not prevent the VBA
References from being viewed, nor any specific library from being "found" in
the path specified.
The alternative, I believe- is to digitally sign your projects, so that you
can register the project with AD as being 'safe'.
One may digitally sign the VBA project, but AD doesn't need to be involved.
(And I assume you are referring to the use of the enterprise policy of
Windows Certificate Services for publishing trusted issued digitial
certificates at a domain level when you mention AD. For others who may be
reading this, for more information on this capability for Windows Server
2000 please see:
http://www.microsoft.com/technet/prodtechnol/windows2000serv/deploy/depopt/2000cert.mspx
or for Windows Server 2003, please see
http://www.microsoft.com/resources/...03/standard/proddocs/en-us/sag_CMCertsCas.asp
and
http://www.microsoft.com/resources/...dard/proddocs/en-us/sag_CSW_Usingpages_WH.asp )
A digital signature that has been identified on a specific computer as a
"Trusted Publisher" can be considered "safe" by Microsoft Access, but
doesn't automatically allow Access to open the file. There are three levels
of digital signatures of "Trusted Publishers": self-certification (which
isn't deemed "safe" when the macro security level is set to high), domain
(or enterprise) level certification (within an organization's network), and
commercial level certification (from a commercial certification authority
such as VeriSign and Thawte). Please see the following Web pages for more
information:
http://msdn.microsoft.com/library/d.../en-us/odeopg/html/deovrsigningvbaproject.asp
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnsmart04/html/sa04d1.asp
I think that in Office XP, this
required Developers' edition..
No Developers' Edition of any version of Microsoft Office has ever been
required in order to digitally sign a VBA project. The ability to digitally
sign a VBA project has been available for all users of Office since
Microsoft Office 2000, and the file to install the self-certify application
for a VBA project is included on the Microsoft Office CD. However, there's
a significant difference between a VBA project and an _Access_ VBA project.
For Access database developers, the issue about the ability to digitally
sign a VBA project in earlier versions of Office is moot, since Microsoft
Office Access 2003 is the first version that one can use to digitally sign
an Access VBA project.
This self-certification isn't the only method to digitally sign the VBA
project for use on multiple computers. One may create a self-certifying
digital certificate and share the private key with other computers, one may
use a digital certificate issued by the organization at a domain
(enterprise) level, or one may purchase a digital certificate issued by a
formal certification authority. Please see the following Web pages for more
information:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnoxpta/html/odc_dsvba.asp
http://www.microsoft.com/downloads/...1F-B313-44F4-8900-3399ABB2001D&displaylang=EN
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnsmart04/html/sa04d1.asp
http://office.microsoft.com/en-us/assistance/HP052495581033.aspx
If I remember it correctly, the standard
editions of Office 2003 will let you do this.
No. The standard edition of Office 2003 cannot be used to digitally sign an
Access VBA project. One must have either Microsoft Office Professional 2003
or Microsoft Office Access 2003 installed on the computer in order to
digitally sign an Access VBA project. This is because one must use
Microsoft Office Access 2003 to open the database file and use the VBA
Editor to digitally sign a specific Access VBA project. One cannot
digitally sign an Access VBA project from within Word, Excel, et cetera.
For the details on digital certificates for Access VBA projects, please read
Rick Dobson's article, "Signing Access 2003 Projects" on the Web page
already listed above:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnsmart04/html/sa04d1.asp
HTH.
Gunny
See
http://www.QBuilt.com for all your database needs.
See
http://www.Access.QBuilt.com for Microsoft Access tips.
(Please remove ZERO_SPAM from my reply E-mail address, so that a message
will be forwarded to me.)
