Runtime

M

Martin

Hi all,

I need to roll out an application that uses Ms Access. The users do not have
Access Instakked. They do hav Ms Office 2003 Standard.
Do I need to install any runtime modules for Access?

Thanks,
Martin
 
R

Rick Brandt

Martin said:
Hi all,

I need to roll out an application that uses Ms Access. The users do
not have Access Instakked. They do hav Ms Office 2003 Standard.
Do I need to install any runtime modules for Access?

Thanks,
Martin
Click to expand...

Yes, they will need either a full (licensed) version of Access or you will have
to purchase the appropriate packages and tools so that you can distribute with
the Access runtime.

If you have no experience with it you should know that an Access app that is
expected to run in the runtime environment needs to be considerably more
"polished" than one that is run in the full Access envioronment. There is no
access to the db window, you have to provide all custom menus and toolbars, you
must have very robust error handling, and there are a few features that the
runtime doesn't support at all (like filter-by-form).

Because of the time and effort necessary for the above (if your app doesn't
already meet those criteria) using the runtime is not really financially
worthwhile unless you have at least half a dozen or more users, If less than
that I would just install full blown Access on their PCs instead.
 
T

Tom Wickerath

Hi Martin,

I recommend reading the following articles:

How to create a distributable Access run-time application by using Microsoft
Office Access 2003 Developer Extensions (Note: includes links for other
versions of Access)
http://support.microsoft.com/?id=842004

Creating a Setup Package Using the Packaging Wizard (Office XP Developer
http://msdn.microsoft.com/library/d...skcreatingsetuppackagewithpackagingwizard.asp

Packaging Wizard (Microsoft Office XP Developer Reference
http://msdn.microsoft.com/library/d...y/en-us/modcore/html/deurfpackagingwizard.asp

A potential trap to be aware of:
You may receive error messages when you install an Access 2002 runtime
deployment package on a computer that is running Windows XP SP2 or Windows
Server 2003
http://support.microsoft.com/?id=837150


Good Luck,

Tom

http://www.access.qbuilt.com/html/expert_contributors.html
http://www.access.qbuilt.com/html/search.html
__________________________________________

:

Hi all,

I need to roll out an application that uses Ms Access. The users do not have
Access Instakked. They do hav Ms Office 2003 Standard.
Do I need to install any runtime modules for Access?

Thanks,
Martin
 
B

Brian

You can install the Access 2003 runtime for all the clients, but you will
need to purchase the Visual Studio Tools for Microsoft Office to get the
Access 2003 Developer Extensions that enable you to package & distribute the
runtime.

As Rick said, though, you have to build ways in VBA to do many of the things
you may take for granted with the full version of Access. I personally think
this is a good idea anyway to prevent users from incorrectly deleting records
when not appropriate, etc.

I believe you can test some or all of this reduced functionality by running
your application with the /runtime command-line switch that emulates the
runtime version (i.e. make a shortcut to "C:\<path>\YourApp.mdb /runtime" and
run it that way). I'm not sure whether this fully emulates the limitations of
the runtime version or not, though.
 
T

Tom Wickerath

Hi Rick,

I completely agree with you, although I'd boost that user base to 15~20
users, minimum. Armen Stein, the past President of the Access User Group that
I am a member of, and the owner of J Street Technology (database consulting
business), shared some advice with our group on this subject. He told our
group that he usually always advises his clients to purchase Access, because
the extra costs involved in dealing with runtime related issues that he would
have to charge will easily pay for copies of Access for each user, when you
are dealing with a small number of users.


Tom

http://www.access.qbuilt.com/html/expert_contributors.html
http://www.access.qbuilt.com/html/search.html
__________________________________________

:
Hi all,

I need to roll out an application that uses Ms Access. The users do
not have Access Instakked. They do hav Ms Office 2003 Standard.
Do I need to install any runtime modules for Access?

Thanks,
Martin
Click to expand...

Yes, they will need either a full (licensed) version of Access or you will
have
to purchase the appropriate packages and tools so that you can distribute
with
the Access runtime.

If you have no experience with it you should know that an Access app that is
expected to run in the runtime environment needs to be considerably more
"polished" than one that is run in the full Access envioronment. There is no
access to the db window, you have to provide all custom menus and toolbars,
you
must have very robust error handling, and there are a few features that the
runtime doesn't support at all (like filter-by-form).

Because of the time and effort necessary for the above (if your app doesn't
already meet those criteria) using the runtime is not really financially
worthwhile unless you have at least half a dozen or more users, If less than
that I would just install full blown Access on their PCs instead.
 
M

Martin

Hi,
Thanks for the reply.

The case here is that the application was built in VB 6.0, using ADO to
connect to a MSAccess database that is situated on a server. So it's a
client-server application.
That's why I reallly don't need full Access installations.
For Acces 2000 I had a good working -alternate- runtime , but I need one for
2003 now.
Maybe I don't need the runtime at all, but just some kind of component
(MDAC??). These are really things I don't know anything about.
Can anyone point me in the right direction?

Greetings,
Martin
 
T

Tom Wickerath

Hi Martin,
...to connect to a MSAccess database...
Click to expand...
Wrong. Your sentence should read "...to connect to a JET database...". In
the scenerio you described, you are not using Access at all.
Maybe I don't need the runtime at all, but just some kind of component
(MDAC??).
Click to expand...
Correct on both guesses. You do not need the runtime, and you do need to
ensure that all client PC's have MDAC installed. VB 6.0 includes the Package
& Deployment Wizard, which should be helpful in packaging your application.


Tom

http://www.access.qbuilt.com/html/expert_contributors.html
http://www.access.qbuilt.com/html/search.html
__________________________________________

:

Hi,
Thanks for the reply.

The case here is that the application was built in VB 6.0, using ADO to
connect to a MSAccess database that is situated on a server. So it's a
client-server application.
That's why I reallly don't need full Access installations.

For Acces 2000 I had a good working -alternate- runtime , but I need one for
2003 now.

Maybe I don't need the runtime at all, but just some kind of component
(MDAC??). These are really things I don't know anything about.
Can anyone point me in the right direction?

Greetings,
Martin
 
M

Martin

Thank you very much, all of you! I am amazed by the enthousiasm in this
group!
For me it's clear now what I need to do: ... nothing, because the setup
takes care of everything!

Keep up the good work!
 
Top