R
Rod Wright
Background:
We developed a program to integrate a large amount of data for National Air
and Space Museum (NASM) volunteer use. The program works fine, but our users
are relatively unsophisticated volunteers. They get confused by the warnings
issued by Access when opening our program. Our users run at multiple Win2K
and XP machines and load our program and the data over the Smithsonian
intranet.
In Vista, the popup warning is:
----------------------------------------------------
Open File - Security Warning
Do you want to open this file?
Name: \\Server\Public\UHC_Frms.exe
Publisher: Unknown Publisher
Type: Microsoft Office Access MDE Database
From: \\SERVER\Public\BLAST\UHC_Frms.mee
| Open | | Cancel |
______________________________________
Note that the path shown above is when I'm testing on my home network, not
at NASM. Also, that warning was from Office 2007 but at NASM they are still
using Office 2003, so the dialog box is different.
Also, the error message is different under Office 2003 (and a lot more
confusing for users.) I'm not at NASM now, so I can't see the exact text of
how the error appears there. I'll post that tomorrow when I go there.
Question:
How can we avoid these warnings? Would it work for us to obtain and publish
a certificate for the program code? If so, does it need to be reissued each
time we make a change? (Since we have only been up and running for users
since January, the code is still being modified as we gain experience.) How
do we do that?
What do you recommend?
We developed a program to integrate a large amount of data for National Air
and Space Museum (NASM) volunteer use. The program works fine, but our users
are relatively unsophisticated volunteers. They get confused by the warnings
issued by Access when opening our program. Our users run at multiple Win2K
and XP machines and load our program and the data over the Smithsonian
intranet.
In Vista, the popup warning is:
----------------------------------------------------
Open File - Security Warning
Do you want to open this file?
Name: \\Server\Public\UHC_Frms.exe
Publisher: Unknown Publisher
Type: Microsoft Office Access MDE Database
From: \\SERVER\Public\BLAST\UHC_Frms.mee
| Open | | Cancel |
______________________________________
Note that the path shown above is when I'm testing on my home network, not
at NASM. Also, that warning was from Office 2007 but at NASM they are still
using Office 2003, so the dialog box is different.
Also, the error message is different under Office 2003 (and a lot more
confusing for users.) I'm not at NASM now, so I can't see the exact text of
how the error appears there. I'll post that tomorrow when I go there.
Question:
How can we avoid these warnings? Would it work for us to obtain and publish
a certificate for the program code? If so, does it need to be reissued each
time we make a change? (Since we have only been up and running for users
since January, the code is still being modified as we gain experience.) How
do we do that?
What do you recommend?