Installing Acces2K Run-time breaks Access2003

[mariantrygg]

Hi

I have an app that uses the a2K run-time. I have just discovered that
installing this app breaks an access2003 installation causing the user
to have to repair the installation using the original installation CD.

I would prefer not to be seen to be 'breaking' customer's computers,
(thanks Microsoft!!!) Does anyone know how to avoid this happening? I
am installing the run-time into a separate folder under my program
folder (C:\program files\mars\AccessRT). I am also installing other
components, such as MDAC2.7 and various windows common controls (6)
but I am very suspicious of the A2K run-time as I know it is
bug-ridden and a rogue to install alongside Access97 anyway.

Anyone come across this and can verify that it is indeed the A2K
run-time that is breaking Acess 2003 or anyone know how to get around
this safely?

Thanks
Marian

[david epsom dot com dot au]

You probably need to buy a third party installation tool,
AND a third party installation script.
"mariantrygg" <ma****@compsols.fsbusiness.co.uk> wrote in message
news:6f**************************@posting.google.c om...

Hi

I have an app that uses the a2K run-time. I have just discovered that
installing this app breaks an access2003 installation causing the user
to have to repair the installation using the original installation CD.

I would prefer not to be seen to be 'breaking' customer's computers,
(thanks Microsoft!!!) Does anyone know how to avoid this happening? I
am installing the run-time into a separate folder under my program
folder (C:\program files\mars\AccessRT). I am also installing other
components, such as MDAC2.7 and various windows common controls (6)
but I am very suspicious of the A2K run-time as I know it is
bug-ridden and a rogue to install alongside Access97 anyway.

Anyone come across this and can verify that it is indeed the A2K
run-time that is breaking Acess 2003 or anyone know how to get around
this safely?

Thanks
Marian

[Tony Toews]

ma****@compsols.fsbusiness.co.uk (mariantrygg) wrote:

I have an app that uses the a2K run-time. I have just discovered that
installing this app breaks an access2003 installation causing the user
to have to repair the installation using the original installation CD.
Yup, there are ways around this but they're a PITA from the customers viewpoint.
I would prefer not to be seen to be 'breaking' customer's computers,
(thanks Microsoft!!!) Does anyone know how to avoid this happening? I
am installing the run-time into a separate folder under my program
folder (C:\program files\mars\AccessRT). I am also installing other
components, such as MDAC2.7 and various windows common controls (6)
but I am very suspicious of the A2K run-time as I know it is
bug-ridden and a rogue to install alongside Access97 anyway.

Anyone come across this and can verify that it is indeed the A2K
run-time that is breaking Acess 2003 or anyone know how to get around
this safely?

The best solution is going to be the Sagekey scripts along with either Wise or
Installshield.

See Microsoft Access (Office) Developer Edition FAQ
http://www.granite.ab.ca/access/developereditionfaq.htm

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 Toews]

Tony Toews <tt****@telusplanet.net> wrote:

The best solution is going to be the Sagekey scripts along with either Wise or
Installshield.

See Microsoft Access (Office) Developer Edition FAQ
http://www.granite.ab.ca/access/developereditionfaq.htm

Actually to be more specific see the Installers section at
http://www.granite.ab.ca/access/runtime.htm

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