Access 2003 Runtime AND Access 2003 on same machine?

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

MS News Groups - 14 Mar 2007 03:02 GMT

I recently bought an un-opened VSTO 2003 on eBay and just installed ADE 2003
(on my XP Pro box). I then used the PDW to deploy a test mdb with a single
form to simply test everything out. I asked it to also deployed A3K
Runtime.

I attempted to install the result on the same XP Pro box (pointed to a
different set of folders so as to now mess up the original mdb), but got a
wierd result. As this box also has Access 2003 installed, the install for
A3K Runtime "seemed" to progress normally (based on all the activity on the
screen), but I cannot see on the system where it was installed. There were
no new folders created that contained msaccess.exe! Did it replace my
"regular" A3K??

As a parallel to this, i can do a similar deal on another computer where I
have A2K and used the A2K developer edition's PDW to create a similar thing.
When I install there, the A2K AccessRuntime installs in a separate folder
from A2K Access --- so they're both on the same computer.

What's the deal with A3K and A3K Runtime. Can't they both be on the same
computer? Or what?

Bob.

Reply to this Message

Tony Toews [MVP] - 14 Mar 2007 06:19 GMT

>What's the deal with A3K and A3K Runtime. Can't they both be on the same
>computer? Or what?

While I haven't tried it I strongly suspect the A2003 runtime is smart
enough that if you already have the A2003 retail installed it doesn't
bother installing the runtime. Just your MDB/MDE, etc.

Tony

Signature

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

Reply to this Message

MS News Groups - 14 Mar 2007 19:12 GMT

Tony,

You had the answer.

The installer recognizes the presence of A3K Retail and (although it seems
to cause a whole lot of activity on the screen with programs being
installed, registry entries being made and a progress bar that indicates
something is going on) it seems to "accomplish" almost nothing.

It also gives no options regarding this situation. It doesn't even give an
option regarding the folder to receive the result.

It could also have something to do with the datestamp on msaccess.exe. The
Runtime exe is dated 08/15/2003 but the Retail exe is dated later (it was
updated when SR-1 was applied).

So I now find I may not be able to have A3K Retail and A3K Runtime on the
same computer (strictly for testing the deploys) --- I'll have to re-arrange
my thinking of how to test the deploys (I'm not talking about testing the
application --- just the deploys). I want to be able use the same computer
to test the application!

Just for "fun" --- I'm going to install A3K Retail on that same computer
(A3K Runtime is installed on it), and see if I can direct the Retail
installer to a different folder. That may be the way to have both on the
same computer!

I'll report back the findings in this thread (probably tomorrow --- I have a
new version of an application to deploy today so it's a busy time here).

By the way, I've already given up on the PDW to do my deploys. I use Inno
Setup, include "msaccess.cab" and "msaccess.msi" in its package, and in my
final phase cause it to execute msaccess.msi passing a command line switch
"qb+" so that the installation is "relatively" quiet, giving only an
indication of progress and a final message indicating completion (or an
error if it failed). This way I have total control of the install and am
not subject to "external" matters. I have a license for Visual Studio 2003
(which includes ADE 2003) so that I am properly licensed to distribute A3K
Runtime.

Also by the way, I like the looks of ADE 2003's Custom Startup Wizard. I
haven't tried it yet, but I like its capabilities (on paper). Right now I'm
doing pretty much all the functions that it performs, but doing them
manually. This may turn out to be much simpler!

Thanks for your help!!!!

Bob.

>>What's the deal with A3K and A3K Runtime. Can't they both be on the same
>>computer? Or what?
[quoted text clipped - 4 lines]
>
> Tony

Reply to this Message

George Nicholson - 21 Mar 2007 17:24 GMT

You can use Access retail to test runtime by using the command line switch
to run your app in "runtime" mode. The command line switch goes back at
least to Access 2000 (not sure about '97).

Create a shortcut on your desktop with the following 3 elements as the
"Target":
"MyPath to msaccess.exe" "MyPath to app front end.mdb" /runtime

This allows you to see how your app will behave under runtime conditions
with a simple click on the shortcut.

The only caveat to this is if the locally installed retail version has
different file versions than the runtime you will be installing (no SP vs
SP1, etc.). Except for these versioning issues, Retail and Runtime Access
use the same set of files.

HTH,

> Tony,
>
[quoted text clipped - 53 lines]
>>
>> Tony

Reply to this Message

Aaron Kempf - 02 May 2007 22:05 GMT

I wish that there was an A3K

maybe they'll have the bugs worked out by then!

> Tony,
>
[quoted text clipped - 53 lines]
> >
> > Tony

Reply to this Message