[AccessD] Error 3027 in A2003 runtime

Jim,

More information: looks like I forgot that when you install a later version
of Office and keep older versions, the newer version "wins" if one simply
opens an Office document. That's all the shortcut was doing. I should have
seen immediately that, hey! There's the ribbon! That ain't Access 2003.

Aha! So I created a desktop shortcut for Access 2003 Runtime and I altered
the properties to add the name of the mde front end file to the Target.

OK. Now I get the old Security Warning: "This file may not be safe if it
contains code that was intended to harm your computer..."

If this were a full install of Access 2003 I would simply change the macro
security setting. But what, if anything, do I have to do to get rid of this
warning in Runtime?

Thank you, Jim.

Sincerely,

Steve Erbach
Neenah, WI


On Tue, Oct 21, 2014 at 7:58 AM, Jim Dettman <jimdettman at verizon.net> wrote:

> Steve,
>
> Make sure:
>
> A. At the file level, the directory and the DB file are not marked
> read-only.
> B. In regards to "A", note that under Windows 7 and on ward, many
> directories are protected and virtualized (their not where you think they
> are).   Put the app in it's own directory.
> C. Make sure the users have full create, read, write, and delete privs for
> the directory where the DB resides.
> D. Check from the command prompt using SET that TMP and/or TEMP environment
> variables point to valid drives and directories and that the user has full
> rights for them.
>
> Jim.
>
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Steve Erbach
> Sent: Tuesday, October 21, 2014 07:38 AM
> To: Access Developers discussion and problem solving
> Subject: [AccessD] Error 3027 in A2003 runtime
>
> Dear Group,
>
> It's been a long while since I logged into AccessD. I use Access for only
> one old project (10-1/2 years) that I've supported for too long, I'm
> afraid.
>
> I recommended that Windows 7 machines be installed for this particular
> client. I also recommended moving from Access 2003 to Access 2010 to sort
> of keep up with the times, eh?
>
> However, my application requires import and export to Paradox v. 4 tables.
> I didn't discover that Microsoft dropped support for Paradox tables (and
> Lotus 1-2-3 spreadsheets) until the program crashed.
>
> So I created an Access 2003 Runtime package with the Developer Tools and
> installed that instead (after UN-installing Office 2010 first, then
> installing the Runtime, then re-installing Office 2010!). But I ran into a
> different problem.
>
> In preparation for importing Paradox data, the app deletes a temporary
> Access table with:
>
> DoCmd.DeleteObject acTable, "xyztable"
>
>
> The app crashes with the 3027 error:
>
> Cannot update. Database or object is read-only.
>
>
> It's been so long that I've worked with the Access Runtime that I don't
> know where to look. The app has worked for 10-1/2 years on Windows XP using
> Access 2003. I didn't remember that there was any particular restriction on
> deleting or creating tables. The table being deleted, by the way, is in the
> front-end.
>
> Could anyone help me with this?
>
> Sincerely,
>
> Steve Erbach
> Neenah, WI
> --
> 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
>



-- 
Regards,

Steve Erbach
Neenah, WI
http://www.NeenahPolitics.com
http://www.TheTownCrank.com