Allen,
did you find any further resolution to this?
I certainly don't know, though I'm aware that there are oftentimes similar
newsgroup requests which also state they have tried the limited suggestions in
the knowledgebase.
There were similar requests in Access2000, and for some reason I never had a
major problem with them, most likely because I GENERATED my packages under
Win2000 or latest Win2000 at the time. I accept that means I avoided the
problem (if I did) more by chance than design.
For Access2002, I tested though never actually implemented. For example, the
ODE2002 Runtime Distributable was never updated by Microsoft (they provided an
SP download on their website, but that was only for upgrading after
implementing e.g. a customer would have to install my CD/Runtime and THEN
upgrade. I wrote (on the internet or newsgroups somewhere), how I incorporated
Service Packs into the distributable A2k2 runtime on one's CD.
I am certainly no expert on the matter, just no-one else had solved it at the
time. It may be "ancillary" to your very specific question, and I've tried, so
far as I can, to take an interest in the issue you raise (runtime installation
issues).
Given your status, it would be very naughty of me to suggest "sagekey"?
By and large, I claim a little more success with ODE than some, perhaps
because I happened to generate with some combination (Win2000 as the base OS
as against WinXP), though never REALLY knowing why things are that way. Also,
it's nearly impossible to test all combinations!
Another apparently little-known issue (in this case A2k ODE), is that A2k
Runtime package installs require a reboot, but WinXP makes a valiant attempt
to suppress reboots. This can have the effect (because I've seen it) that when
an installation is not actually complete, and a customer signs on a different
way to a PC such as change-of-shift workers, the result can be that the
ODE-generated package offers to de-install my software rather than finish the
installation! That's what I claim. I thought I was just about the only one
left who persevered with ODE (as against Sagekey) installations.
I neither have nor collect info nor even express interest in, later versions
of Access than 2002.
Regards
Chris
"Allen Browne" <AllenBrowne[ at ]SeeSig.Invalid> wrote in message
news:utkXPLomGHA.4992[ at ]TK2MSFTNGP03.phx.gbl...
[Quoted Text] > I used the Access 2002 packaging wizard to create a runtime installation. > Installs fine on Windows XP. > > On a fully-patched Windows 2000 SP4, client reports the installation fails > with a message that it > ... cannot be installed on this system because it > requires Windows NT 4.0 Service Pack 6 or later. > > It is not this issue: > http://support.microsoft.com/?id=837150> I double-checked, and Dbmsadsn.dll was removed from Ospfilelist.txt long > ago. (In any case that kb does not apply to Win2000.) > > Any suggestions? > > -- > Allen Browne - Perth, Western Australia. > Tips for Access users - http://allenbrowne.com/tips.html> Reply to group, rather than allenbrowne at mvps dot org. > >
|