D
dbuschmohle
Hello,
I currently have an Access 2007 project that we use for our company’s
inventory system. A few months back, we upgraded some users to the full
version of office, and now I am attempting to setup some other users with the
2007 Runtime version and have some questions...
If the computer that the user is using already has Access 2007 Runtime
installed on it, should I still be making an MSI installer package for them
to run, or can I simply copy an ADE file to their computer...? I have
actually tried both ways but wasn’t sure which was the best practice.
When I tried putting an ADE file on a computer that has Access 2007 Runtime
installed on it, the ADE file appears to work fine, except when launching I
receive an error message stating the the code could be unsafe. I assumed
this was a security setting issue that could not be changed because it is
Runtime, so I installed a VeriSign certificate and digitally signed my code,
and still received the message... If copying an ADE file to a computer with
Access 2007 Runtime is an accepted practice, then how do I stop this message
from appearing...?
As I mentioned before, I also attempted to package my code using the Access
2007 developer extensions, but had a couple questions with that method as
well. Normally, I take my main ADP file, and create and ADE files to deploy
to my users. Does it make any difference whether I create my Runtime package
from the ADP or ADE file...? Also, in working with the ACCDR file format, I
found that by simply renaming the file extension to ADE, a user can see the
table data and VBA code... Does this mean the only thing really done when
changing to Runtime format is to change the file extension...?
Thanks,
-Dave
I currently have an Access 2007 project that we use for our company’s
inventory system. A few months back, we upgraded some users to the full
version of office, and now I am attempting to setup some other users with the
2007 Runtime version and have some questions...
If the computer that the user is using already has Access 2007 Runtime
installed on it, should I still be making an MSI installer package for them
to run, or can I simply copy an ADE file to their computer...? I have
actually tried both ways but wasn’t sure which was the best practice.
When I tried putting an ADE file on a computer that has Access 2007 Runtime
installed on it, the ADE file appears to work fine, except when launching I
receive an error message stating the the code could be unsafe. I assumed
this was a security setting issue that could not be changed because it is
Runtime, so I installed a VeriSign certificate and digitally signed my code,
and still received the message... If copying an ADE file to a computer with
Access 2007 Runtime is an accepted practice, then how do I stop this message
from appearing...?
As I mentioned before, I also attempted to package my code using the Access
2007 developer extensions, but had a couple questions with that method as
well. Normally, I take my main ADP file, and create and ADE files to deploy
to my users. Does it make any difference whether I create my Runtime package
from the ADP or ADE file...? Also, in working with the ACCDR file format, I
found that by simply renaming the file extension to ADE, a user can see the
table data and VBA code... Does this mean the only thing really done when
changing to Runtime format is to change the file extension...?
Thanks,
-Dave