By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
434,933 Members | 1,223 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 434,933 IT Pros & Developers. It's quick & easy.

Installling A97 runtime app onto Windows 2000 Professional machine

P: n/a
MLH
My firsta attempt at rolling out an Access 97 runtime installation
onto a Windows 2000 Professional box did not go too well. The
installation itself was bumpy. Afterward, attempts to run the app
were met with O.S. messages complaining that the machine was
not licensed to run the application. Hmmm??? Ideas / comments?
Dec 18 '06 #1
Share this Question
Share on Google+
7 Replies


P: n/a
On Mon, 18 Dec 2006 07:50:08 -0500, MLH <CR**@NorthState.netwrote:

Didn't I tell you to bookmark this site?
http://www.mvps.org/access/bugs/bugs0013.htm

-Tom.

>My firsta attempt at rolling out an Access 97 runtime installation
onto a Windows 2000 Professional box did not go too well. The
installation itself was bumpy. Afterward, attempts to run the app
were met with O.S. messages complaining that the machine was
not licensed to run the application. Hmmm??? Ideas / comments?
Dec 18 '06 #2

P: n/a
On Mon, 18 Dec 2006 07:50:08 -0500, MLH <CR**@NorthState.netwrote:
>My firsta attempt at rolling out an Access 97 runtime installation
onto a Windows 2000 Professional box did not go too well. The
installation itself was bumpy. Afterward, attempts to run the app
were met with O.S. messages complaining that the machine was
not licensed to run the application. Hmmm??? Ideas / comments?
This is a know bug caused (believe it or not by a font. (Hatten.ttf)

see http://support.microsoft.com/?id=141373

Wayne Gillespie
Gosford NSW Australia
Dec 18 '06 #3

P: n/a
MLH
Honestly, I don't remember. You may have. I don't recall rolling
a '97 runtime app out onto a Win2k box before now. I'll check
the link.
On Mon, 18 Dec 2006 06:53:31 -0700, Tom van Stiphout
<no*************@cox.netwrote:
>On Mon, 18 Dec 2006 07:50:08 -0500, MLH <CR**@NorthState.netwrote:

Didn't I tell you to bookmark this site?
http://www.mvps.org/access/bugs/bugs0013.htm

-Tom.

>>My firsta attempt at rolling out an Access 97 runtime installation
onto a Windows 2000 Professional box did not go too well. The
installation itself was bumpy. Afterward, attempts to run the app
were met with O.S. messages complaining that the machine was
not licensed to run the application. Hmmm??? Ideas / comments?
Dec 18 '06 #4

P: n/a
MLH
Hmmm??? I reran the runtime setup using setup /y. It failed
saying the application was not set up properly at the end of
it all. Should I have uninstalled the app before running setup /y?
Dec 18 '06 #5

P: n/a
MLH
Perhaps the procedures at the site you
recommended do not apply to runtime
installations. It seems they mention a
great deal about the full retail version
of Access 97 and Office 97, but say
nothing specifically of runtime. I may
be hosed - dunno.
Dec 18 '06 #6

P: n/a
Wayne Gillespie wrote:
On Mon, 18 Dec 2006 07:50:08 -0500, MLH <CR**@NorthState.netwrote:
My firsta attempt at rolling out an Access 97 runtime installation
onto a Windows 2000 Professional box did not go too well. The
installation itself was bumpy. Afterward, attempts to run the app
were met with O.S. messages complaining that the machine was
not licensed to run the application. Hmmm??? Ideas / comments?

This is a know bug caused (believe it or not by a font. (Hatten.ttf)

see http://support.microsoft.com/?id=141373

Wayne Gillespie
Gosford NSW Australia
Rather than say that a bug is caused by the font, perhaps it is more
accurate to say that the existence of the font file is used as a
software switch in such a way that it is often necessary to rename the
font temporarily as part of solving the problem.

James A. Fortune
CD********@FortuneJames.com

Dec 19 '06 #7

P: n/a
On 19 Dec 2006 13:40:30 -0800, CD********@FortuneJames.com wrote:
>>
This is a know bug caused (believe it or not by a font. (Hatten.ttf)

see http://support.microsoft.com/?id=141373

Wayne Gillespie
Gosford NSW Australia

Rather than say that a bug is caused by the font, perhaps it is more
accurate to say that the existence of the font file is used as a
software switch in such a way that it is often necessary to rename the
font temporarily as part of solving the problem.

James A. Fortune
CD********@FortuneJames.com
Perhaps
Wayne Gillespie
Gosford NSW Australia
Dec 20 '06 #8

This discussion thread is closed

Replies have been disabled for this discussion.