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

Access 2003 Runtime

P: n/a
I am looking at installing an Access 2003 application on some machines
that don't have any version of Access previously installed. After
reading lots of posts on this group and elsewhere I assume that I need
to purchase "Visual Studio Tools For Office 2003" which will give me
the ability to install the application together with the Access
runtime. I also assume I will also have the legal right to distribute
the runtime.

Most of the problems that I have read about when installing the runtime
seem to stem from the target machines having other versions of Access
already installed. Given that my target machines will not have any
version of Access previously installed on them, can I reasonably expect
to install the app and run it reliably by using the runtime or are
there other issues to consider? Also can I perform the install
successfully without resorting to third party installers?

Any help is appreciated.

Nov 24 '05 #1
Share this Question
Share on Google+
5 Replies


P: n/a
Wayne wrote:
I am looking at installing an Access 2003 application on some machines
that don't have any version of Access previously installed. After
reading lots of posts on this group and elsewhere I assume that I need
to purchase "Visual Studio Tools For Office 2003" which will give me
the ability to install the application together with the Access
runtime. I also assume I will also have the legal right to distribute
the runtime.

Most of the problems that I have read about when installing the
runtime seem to stem from the target machines having other versions
of Access already installed. Given that my target machines will not
have any version of Access previously installed on them, can I
reasonably expect to install the app and run it reliably by using the
runtime or are there other issues to consider? Also can I perform
the install successfully without resorting to third party installers?

Any help is appreciated.


You're correct that most problems with the runtime occur on machines that have
another version. Without that the runtime is fairly easy to deal with. Access
2003 does require Windows 2003 SP3 or higher. Will all of the target PCs meet
that spec?

I'm not that familiar with the 2003 installer, but can't see any reason why it
wouldn't work.
--
I don't check the Email account attached
to this message. Send instead to...
RBrandt at Hunter dot com
Nov 24 '05 #2

P: n/a
Hi Rick. I'm assuming you meant Windows 2000 SP3. Yes, all the target
PCs meet that spec.

Nov 24 '05 #3

P: n/a
Wayne wrote:
Hi Rick. I'm assuming you meant Windows 2000 SP3. Yes, all the
target PCs meet that spec.


Doh! Of course. If I cuold tpye I'd be dngreus.

--
I don't check the Email account attached
to this message. Send instead to...
RBrandt at Hunter dot com
Nov 24 '05 #4

P: n/a
I've been playing with the Access 2003 runtime included on the Office
CD. I've installed it on to a clean machine and it works well except
for the security warnings when I open a database. I know that it is a
simple matter of changing macro security to "Low" when using the full
version of Access. How do I achieve this when using the runtime
version. Is there a simple solution?

Nov 24 '05 #5

P: n/a
Set (or create) two registry keys

HKEY_LOCAL_MACHINE\Software\Microsoft\Jet\4.0\Engi nes
Name: SandBoxMode
Value: 2 (dword)
This key should exist, and the default is 2.

HKEY_LOCAL_MACHINE\Software\Microsoft\Office\11.0\ Access\Security
Name:Level
Value: 1 (dword)
This key usually needs to be created.

You can limit the effect to the user level by using HKEY_CURRENT_USER
instead for the latter key.

Search the string "access 2003 sandboxmode" in this group and you will
find a useful thread

By the way, the 2003 runtime is noticeably more stable and easier to
install and maintain than prior versions. We run it on a few individual
PCs in our company, some with 97 already installed; and on the servers in
our Citrix server farm, completely without incident for 3 months.

Richard Bernstein

"Wayne" <cq*******@volcanomail.com> wrote in
news:11**********************@g49g2000cwa.googlegr oups.com:
I've been playing with the Access 2003 runtime included on the Office
CD. I've installed it on to a clean machine and it works well except
for the security warnings when I open a database. I know that it is a
simple matter of changing macro security to "Low" when using the full
version of Access. How do I achieve this when using the runtime
version. Is there a simple solution?


Nov 25 '05 #6

This discussion thread is closed

Replies have been disabled for this discussion.