Future of Access 2003 Runtime Solutions

[makoilija]

Facts for Access 2003 / Office 2003 version:

1. Visual Studio 2005 Tools for the Microsoft Office System (VSTO) to get
the licence to distribute a run-time version of Access including developer
extensions for making setup packages.

2. Macro security for security level (global setting)

Now to the point: how can the solution be done without third party digital
signature for .MDE solution using dynamic queries (new/modifying existing
queries) on code run (VBA) ?

As start up user have to get security level to low before the solutions
flows as designed. This means a lot of explanations, documentation and worst
of all, in the case of high security level, deep diving into the windows
registry with regedit to modify the level value.

The application is targeted for Small Business sector ('workgroup'). How
many Euros more do we have to spend to get things done as they should be
done, without user annoying experiences ?


Pekka Makkonen

Sowtware Developement Manager

 

[Cindy M.]

Hi =?Utf-8?B?bWFrb2lsaWph?=,

Since you haven't gotten any response here, try in an Access-specific
newsgroup. You're more likely to get a discussion going where numerous Access
people congregate

Facts for Access 2003 / Office 2003 version:

1. Visual Studio 2005 Tools for the Microsoft Office System (VSTO) to get
the licence to distribute a run-time version of Access including developer
extensions for making setup packages.

2. Macro security for security level (global setting)

Now to the point: how can the solution be done without third party digital
signature for .MDE solution using dynamic queries (new/modifying existing
queries) on code run (VBA) ?

Cindy Meister
INTER-Solutions, Switzerland
http://homepage.swissonline.ch/cindymeister (last update Jun 17 2005)
http://www.word.mvps.org

This reply is posted in the Newsgroup; please post any follow question or
reply in the newsgroup and not by e-mail