[AccessD] Run-Time Problem

But won't that still leave me with the problem of getting shut out with that
security restriction message? 


Rocky Smolin
Beach Access Software
858-259-4334
www.e-z-mrp.com
www.bchacc.com
 
 

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Doug Murphy
Sent: Wednesday, December 03, 2008 6:20 PM
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] Run-Time Problem

Get the latest Sagekey scripts for what ever version of Access your using,
and all the jet, MDAC, IE updates.  Sagekey put out several new versions of
their scripts to handle the Vista security issues. They do cost additiona
money.

Doug 

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Rocky Smolin at
Beach Access Software
Sent: Wednesday, December 03, 2008 4:15 PM
To: 'Access Developers discussion and problem solving'
Subject: [AccessD] Run-Time Problem

Dear List:

I gave a run-time install to a client - I actually went and installed it on
several machines - but one machine I didn't do.  So today the user ran the
Setup.exe, which I created using Wise/SageKey - works just dandy - installed
it, started the mdb.  Now to get into the program you have to answer three
questions correctly, the first one of which is about blocking unsafe
expressions.  The answer should be No.  He clicked Yes.  Of course, the
program wouldn't open.

Now the problem, when he goes in again the mdb won't start, won't even get
to the first of the questions.  Instead he gets a message that the mdb
cannot be opened due to security restrictions.  And bails out.  So I had him
copy the mdb from another location where it was working, on the theory that
it was the mdb that was flagged as blocked.  But that didn't help.  So I
figured the restriction is set in the run-time somewhere so I had him
uninstall the Runtime from the Add/Remove programs in the control panel and
reinstall.  But no luck.

So, how do I get the Access run-time install to ask again about blocking
unsafe expressions so they can get back into the mdb?

 

MTIA,

 

Rocky

 

 
--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com

--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com