[AccessD] Access2010 Runtime problem

FWIW, I discovered that the remedy to the read-only constraint is to make
the runtime folder shareable. This makes no sense, of course, because now I
have to set the share status on the installation folder on every workstation
before  I distribute the package. If anybody knows a way around this, I'd
love to hear it. 

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Darrell Burns
Sent: Wednesday, August 31, 2011 1:08 PM
To: 'Access Developers discussion and problem solving'
Subject: [AccessD] Access2010 Runtime problem

I have an app that's been developed in A2010 on my Windows7 machine running
Office2010 32bit. Autoexec runs a proc called "AddTrustedLocation" (which I
picked up from UtterAccess) that inserts registry settings to add the app's
current database as a trusted location. I created a runtime with the Package
Wizard, tested it on the same development box and everything works
fine...the registry settings are properly updated and the app opens into the
Switchboard. But when I install the runtime on a different Windows7 machine
(also with Office 2010) it crashes on opening. I confirmed that the folder
is trusted via the registry settings.

So I disabled the Autoexec and all the Switchboard startup procedures. At
least the app opens the Switchboard, but now I get a "This database has been
opened read-only" message. I suspect that this is why it was crashing before
I disabled everything. This is a front-end to a SQLServer database but I do
have a few local tables I use for temporary storage, so read-only is a
show-stopper. The folder it's in has full privileges. I confirmed this by
copying in the accdb version, and it works just fine. What would be the
cause (and remedy) for this condition?

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