"Rick Brandt" <ri*********@hotmail.com> schreef in bericht news:bS*******************@newssvr11.news.prodigy. com...
The "original" question was why is MLH seeing these warnings when installing his
97 runtime app. My point was that getting those warnings has nothing to do with
"outside dependencies". If he was packaging and installing a data only mdb with
zero references he would still have gotten those messages.
Yep, that's also my experience.
In almost all my A97-runtime-distributions (zero dependencies) I got these two warnings.
I *always* ignored them without any other problems, but I was a bit pissed, because I did *not* want to deliver apps that way.
I like 'proper' install sets ... without any warnings. I like my users to think. "hey, that is working great."
In 'my days of Access 2.0' I also used a runtime install set.
When using User Level Security I *had* to 'manually' set certain things 'right'.
The runtime-install was always messing-up the mda (and I believe the ini-file) that was to be used ...
Aaarrrrrgggghhhhhhhhhhhh !!!!!!
Eventually I 'got this right' by means of a batch-file that I started automatically after the improper-install.
I *never* managed to 'get right' the Access 97-runtime-install (without warnings that is ...)
For a co-project I was involved with, we once made a A97-Wise-install with the SageKey script. It worked !!
I hate to have to buy third-party software (Wise + Sagekey) only to get software that I payed for to work properly ...
I still think it is a real shame that MS did such a terrible job at this.
Later developer-editions are the same misery I believe from postings here ??
For me: I will *never* buy a developers-kit again until it is a proper one.
A year ago or so I decided (as others here) to deliver only to clients that have (or will buy) Access installed on their system.
I also was thinking of eventually delivering A97 installs on 'clean' systems. (see further on)
(I don't want the install to mess up a system where Office is installed...)
Two weeks ago I had to re-install a A97-program for a client on two brand new PC's.
Guess what??
The A97-runtime-install that I have used *for years* for this client (with the 2 warnings MLH asked about) failed !!
It just did not work. I kept recieving GPF's ...
Client had Win '98 SE before, but on these new PC's we had Windows XP-home sp2 installed. *Nothing* else!
So I decided to convert the app to A2k and tried to install Office 2000 instead of the runtime.
==>> I did 'uninstal' the runtime of course!!
Guess what??
The Office2000 install failed !! This was ONLY because I *did have tried* to install the A97-runtime.
I even tried to get back to the original registry and all. (used the WinXP /restore or whatever switch.)
Even that did not work !!
I had to *completely rebuild!!* that system... Aaarrrrrgggghhhhhhhhhhhh !!!!!!
After I did that I installed Office 2k and the app worked...
So now I am stuck with two versions (A97 AND A2k) of the *same* app running in several shops.
I am still happy to be able to use the same A97 backend for both versions.
But I really thank God (almost daily) that the A2k mde runs with A2k2 and A2k3 ...
Sorry: had to get this off my chest ... ;-)
Arno R