The ABC's of Application Distribution

[Jay]

Hi –

I’m nearing the end of development for a small Access application and I’m
starting to think about beta testing and distribution. I’ve developed the
application completely in Access 2003 (I don’t own, nor have I used any
“developer’s editions" or tools like Visual Studio). I need advice on
preparing & packaging the application for distribution.

What are the essentials of distribution? For example, should I obtain the
Access 2007 runtime and developer extension or should I purchase Visual
Studio Tools for MSOffice for more compatibility with Access 2003? Are any
of these developer tools absolutely necessary? If Access 2007 runtime and
developer extensions are used, are they known to conflict with Office 2003
installations?

Thanks in advance for any sage advice you can provide regarding the ABC’s of
distribution.
Jay

 

[Allen Browne]

If all your clients have a copy of Access 2003 or 2007 installed on their
computer, you can give them the database and they can use it.

If some clients do not have Access, you will need something like the A2007
runtime, or they will have to buy Access.

If you plan to use the runtime, make sure you have used code (not macros),
with error handling in every procedure.

Whether you use the runtime or not, it is a good idea to split the database
(so you can update the front end without overwriting their data), and to use
an MDE (if you don't want people modifying your code, forms, or reports.)

One option you might consider is installing a Virtual PC so you can learn
and test what happens when you install the runtime.

 

[Jay]

Thank you Allen. I'll keep your recommendations in mind as I
(asymptotically) approach completion. I'll especially look into installing a
Virtual PC and testing my application with both A2003 and A2007 runtime
components.

Thanks again,
Jay

 

[Tony Toews [MVP]]

What are the essentials of distribution? For example, should I obtain the
Access 2007 runtime and developer extension or should I purchase Visual
Studio Tools for MSOffice for more compatibility with Access 2003?

It could be very difficult to locate VSTO for A2003 now. You may
locate copies on Ebay however it's unknown how legitimate they are.

The A2007 runtime is free of course.

Are any
of these developer tools absolutely necessary?

Only if you want to allow uses to install your app without having a
retail copy of Access present.

If Access 2007 runtime and
developer extensions are used, are they known to conflict with Office 2003
installations?

Conflict in the sense that each user will typically run their apps and
your apps in the last version of Access which was executed. Which may
not be appropriate for either of you.

I use an Inno script, derived from Albert Kallal's script, to check
various registry keys to see if a version of Access from 2000 to 2007
is installed. If not then they have to download a runtime. If A2000
to A2007 is installed then the Inno script will continue the install
and they can run the app. I have created the MDE in A2000 format and
will continue to do so for some time to come.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/

 

[Jay]

Thanks Tony. Very useful information. Do you know if there are any problems
with simply distributing VSTOR.exe runtime to all users, regardless of
whether they have Access installed? In other words, why go through the
process of packaging a custom Access MDE and managing the installation with
scripts if you can distribute the MDE/VSTOR.exe as a unit to everyone?

I’ve located what looks to be a backward-compatible, VSTO 2005 SE Runtime
(VSTOR.exe) download at:

http://www.microsoft.com/downloads/...CB-B43E-4B09-82F6-8BA3F7B5E935&displaylang=en

If installing VSTOR.exe on a PC that has Access installed, I guess I’ll look
into the Inno scripts you describe and then install VSTOR.exe or not
depending on the user’s environment.

Jay

 

[Tony Toews [MVP]]

Thanks Tony. Very useful information. Do you know if there are any problems
with simply distributing VSTOR.exe runtime to all users, regardless of
whether they have Access installed? In other words, why go through the
process of packaging a custom Access MDE and managing the installation with
scripts if you can distribute the MDE/VSTOR.exe as a unit to everyone?

I have no idea what VSTOR.exe is. I'm also not a lawyer so I don't
answer EULA questions. I do have the VSTO A2003 runtime though but
I'd have to poke about a bit.

Ok, when I take a look at the following URL that's not the Access
runtime. I'm not at all sure what else the VSTO does as I've never
gotten around to looking at it.

I’ve located what looks to be a backward-compatible, VSTO 2005 SE Runtime
(VSTOR.exe) download at:

http://www.microsoft.com/downloads/...CB-B43E-4B09-82F6-8BA3F7B5E935&displaylang=en

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/

 

[Jay]

I need to do some more research, I guess. I thought VSTOR.exe was the Access
runtime component, but it looks as if it's not. I'll study application
deployment a bit more and, if questions remain or I find some valuable
information, I'll start a new post thread on the subject.

Thanks again for all the information leads.

Jay