Runtime problem

[summerwind]

I have distributed my app to a few users without problems (Not too many
anyway) using the packaging wizard.

I now have a problem that it causing me a great deal of concern.

My client has no MS Office app on either of his machines (One running
W98 the other XP). However, he does have MS Works and MS Money on both
machines.

I sent him a CD with runtime setup package and my app. Runtime would
not install. OK - I created another CD, tested it on a machine that did
not have Access - worked perfectly.

Client still cannot install runtime although the folders for my app are
created on his machines.

Access simply will not run on either of his machines.

Please help, I have no idea where to go from here.

[Rick Brandt]

summerwind wrote:

I have distributed my app to a few users without problems (Not too
many anyway) using the packaging wizard.

I now have a problem that it causing me a great deal of concern.

My client has no MS Office app on either of his machines (One running
W98 the other XP). However, he does have MS Works and MS Money on both
machines.

I sent him a CD with runtime setup package and my app. Runtime would
not install. OK - I created another CD, tested it on a machine that
did not have Access - worked perfectly.

Client still cannot install runtime although the folders for my app
are created on his machines.

Access simply will not run on either of his machines.

Please help, I have no idea where to go from here.

Please clarify "...does not install...". Are errors raised?

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

[Albert D. Kallal]

Well, the first thing here is that you fail to mention what version of the
runtime you are using.
(in fact, since you left out this information, then it kind shows you are
missing details on a regular basis about troubleshooting. By leaving out
this information, you kind of are pointing out the starting bases of your
problem. To leave out such important information in your troubleshooting
process gives me little, or no ability to narrow down what the problem could
be).

So, I can give a few general pointers here:

Do remember that installing ms-access (or the runtime) means in plain
English that you are installing a VERY LARGE application. Further all of the
problems that you have when installing multiple versions of ms-access (or
office) on pc remain. Since the runtime is essentially ms-access, then the
problems of multiple versions of ms-access on a target machine remain. And,
if you have not had experience installing ms-access, and installing
ms-access on machines with more then one version, then again you are in for
a rough ride.

Since you are missing basic information in your post about what version you
are using, then probably at this point, you might want to "purchase" some
experience of others who gone through installing ms-access on "many"
machines.

A good starting point would be sagekey

www.sagekey.com
--
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada
pl*****************@msn.com
http://www.members.shaw.ca/AlbertKallal

[Deano]

Albert D. Kallal wrote:

Well, the first thing here is that you fail to mention what version
of the runtime you are using.
(in fact, since you left out this information, then it kind shows you
are missing details on a regular basis about troubleshooting. By
leaving out this information, you kind of are pointing out the
starting bases of your problem. To leave out such important
information in your troubleshooting process gives me little, or no
ability to narrow down what the problem could be).

So, I can give a few general pointers here:

Do remember that installing ms-access (or the runtime) means in plain
English that you are installing a VERY LARGE application. Further all
of the problems that you have when installing multiple versions of
ms-access (or office) on pc remain. Since the runtime is essentially
ms-access, then the problems of multiple versions of ms-access on a
target machine remain. And, if you have not had experience installing
ms-access, and installing ms-access on machines with more then one
version, then again you are in for a rough ride.

Since you are missing basic information in your post about what
version you are using, then probably at this point, you might want to
"purchase" some experience of others who gone through installing
ms-access on "many" machines.

A good starting point would be sagekey

www.sagekey.com

And if you choose to buy the Access Runtime MSI Wizard do drop me a line so
I know I'm not the only person using the software :)

[summerwind]

Hmmm.

The version I am using is Developer 2002. This however is a side issue
as the client has no copy of Access on either machine.

I don't need to purchase experience of installing Access as I have done
it myself hundreds, if not thousands of times before. That is why this
problem is so perplexing.

The runtime package does not produce any error messages on this
client's machines - it simply doesn't install - full stop. It does
create the folder for my application however.

The very same CD installed on a clean machine before I sent it to him
so I am fairly confident that it is not software I sent, but something
on his machines. That is why I mentioned MS Works and MS Money.

I should perhaps add that I have installed runtime on machines in the
past that had a version of Works but produced no problems.

[Albert D. Kallal]

Ok, I did not want to sound like a nag, but at least we need some starting
point here:

The version I am using is Developer 2002. This however is a side issue
as the client has no copy of Access on either machine.

Well, no, not necessary a side issue. I mean, if you go all the way back to
a97, and install it on a brand new machine, it works fine if the user got
full registry permissions, and the user that installs the software has full
admin permissions. However, trying to install a97 on a new machine with
limited
permissions generally causes all kids of problems.

The later versions (such as a2002) have provisions for registry security,
and respect this during install (so, they are MUCH more tolerant when you
install on a machine with limited registry settings, since they were
designed with this in mind. With a97, it was designed long before things
like individual users could have permissions set on the registry. Thus, a97
experience more problems in this area.). Also, a good many machines today
have the "program files" directory set to read only to prevent virus spread,
and again older versions of software DO NOT function well, but later
versions
can happily function with a "read only" program files directory.

So, it is VERY important to at least know what version you are talking
about, and what target platform.

The area you might start to check is the company using a domain server?
(that means all permissions for each desktop is set on the server, and that
also includes things like registry permissions, and what a user is allowed
to
do - such as installing software).

So, I would start looking at the security settings

Can a user with full admin permissions to the machine , and registry
settings install the software?

--
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada
pl*****************@msn.com
http://www.members.shaw.ca/AlbertKallal