By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
434,709 Members | 2,211 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 434,709 IT Pros & Developers. It's quick & easy.

Digital Certificate question

P: n/a
We have an application developed by one developer. He compiled the
database into an application and digitally signed the application. He
doesn't know if he used selfcert of makecert to make the key.

The problem is I am creating additional forms now for the database on
a different machine. Whenever we try and incorporate the forms I
develop into the application, the application fails on some users'
machines. We suspect it is because I am not developing with the same
digital certificate the application was originally signed with.

Do I need to import the the original digital certificate for my
development efforts?
If so, how do I do that?

Thanks.

Troy Lee
Sep 30 '08 #1
Share this Question
Share on Google+
5 Replies


P: n/a
What do you mean by "application fails"? Do the changes not save or does the
db not open afterwards? What's the error message?

If he used self sert the app will only open on his pc without the security
messages if he has macro security set to medium, the other pcs will show the
security messages if they don't have macro security set to low.

If you modify the design, you invalidate that certificate. You need to
purchase your own digital certificate if you're developing databases for an
audience that requires digital signatures. OTH if this other developer is in
your organization, after your changes he can sign the db with the digital
certificate he has set up on his pc. Or work with your network admins to set
up the organizational digital certificate on your pc too.

Chris
Microsoft MVP
tr******@comcast.net wrote:
>We have an application developed by one developer. He compiled the
database into an application and digitally signed the application. He
doesn't know if he used selfcert of makecert to make the key.

The problem is I am creating additional forms now for the database on
a different machine. Whenever we try and incorporate the forms I
develop into the application, the application fails on some users'
machines. We suspect it is because I am not developing with the same
digital certificate the application was originally signed with.

Do I need to import the the original digital certificate for my
development efforts?
If so, how do I do that?
--
Message posted via http://www.accessmonster.com

Sep 30 '08 #2

P: n/a
Thanks for the response.

The failure we get is that the application won't execute after
install. Access indicates some type of fatal error and closes. This
only happens on some machines, of which some only have runtime. This
is a real pain and no one seems to know why this is happening? Your
thoughts please.

Troy Lee

Sep 30 '08 #3

P: n/a
The most common reason for a db app to close with a fatal error and no error
message with the Access runtime is from poor vba coding and inadequate
testing and error handling. The runtime requires a robust design and coding.

Look at the new forms you added. How many procedures don't have any error
handling or rely on "On error resume next"? If it's more than zero, start
adding error handling.

Chris
Microsoft MVP
tr******@comcast.net wrote:
>Thanks for the response.

The failure we get is that the application won't execute after
install. Access indicates some type of fatal error and closes. This
only happens on some machines, of which some only have runtime. This
is a real pain and no one seems to know why this is happening? Your
thoughts please.
--
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/For...ccess/200809/1

Sep 30 '08 #4

P: n/a
Thanks a lot. I will look at this a little closer. I was not aware of
the stringency of runtime.
Sep 30 '08 #5

P: n/a
Make sure it compiles, too. It's easy to forget that step after importing a
bunch of new forms.

Chris
Microsoft MVP
tr******@comcast.net wrote:
>Thanks a lot. I will look at this a little closer. I was not aware of
the stringency of runtime.
--
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/For...ccess/200809/1

Sep 30 '08 #6

This discussion thread is closed

Replies have been disabled for this discussion.