I created a VBA program (Access). When running XP at medium security , the User receive a message at startup about no digital certificate .
How do I by- pass this warning
Printable View
I created a VBA program (Access). When running XP at medium security , the User receive a message at startup about no digital certificate .
How do I by- pass this warning
Sign your VBA project with a digial certificate and then you can change the security level to high - run only signed code.
Thanks Rob, I do have a digital certificate, and this program is running our network; I wrote it. I installed this program on several PCs and the boss does not like seeing the warning message. I am guessing I need to sign each PC and the server,or by-pass it. I do not know how. Any advice ?
Yes, each workstation will need its own cert. This is my FAQ on it - http://vbforums.com/showthread.php?t=402030
Thanks again. I might still have a question...as soon as I know what the question is, I will post it.
Moved.
Thank you for your prompt reply...
I understand that i need a digital cert to avoid the warning, and that high security won't open the db w/o a cert, and i have looked at your faq. The remaining problem is this:
I am trying to install the package in question on workstations that do not have any office programs installed. I used the package wizard and signed the project beore i compiled it (if that is what it is doing). The installation package installed the Access runtime environment, and that is what we are running under.
As you showed in your FAQ, i can create the cert on a machine with office tools, but since the workstations in question do not have office installed, i cannot see any way to create the cert on those workstations.
In a perfect world, it would seem that there should be some way to point the
appliation to the LAN server to find a private cert.
Certs created with the SELFCERT.EXE office utility are for private use as they are generated off of a hardware alogorthium of the machine its generated on. So if you were to move a cert to another machine then it will not be valid.
You would need a public certificate (costs $) in order to sign projects where office is not installed, but that brings up the question:
If the system doesnt have Office installed, how could you be running Access via its GUI?
We are running the package in access runtime which is installed on the workstation by the installer. The installer is made using access developer extensions packaging wizard on our development machine.
There may be something in the Access Developer Extensions but I never looked in depth.
If you have a windows server OS available install certification services on it if it isn't by default, generate a certificate, sign the app with the certificate.
If you're in a windows domain you can make the certificates automatically trusted for all workstations with certification services, otherwise the workstation has to install the certificate and say the certificate is trusted.
Does anyone has more information on this subject, my office is having the same problem, how to create an in-house certification or by-pass...thanks