Error in Runtime 97 after upgrade to Win XP

[Kathryn Townsend]

We have a customer using our Acc97 Runtime application on a Win 98
machine that was recently upgraded to WinXP Home Edition Service Pack
1. Shes states RAM is 228, CPU Pentium II 398 MHz , Hard drive 7.85
GB with 795 MB free space. Retail Access is NOT installed, Word and
Excel 9 ARE installed.

When first starting our app she got the message "Microsoft Acess can't
start because there is no license for it on this machine."

She reinstalled our app and LICENSE MESSAGE WAS RESOLVED but then
began getting error messages related to formats.

1. When she opens our program she gets a one-time error (each time
app is opened) of:

can't load the (partial data from a function name that runs in
autoexec) format. The setting for this format in the Windows Registry
is incorrect. You can't save the output data to a file in this
format until you correct the setting in the registry. Run setup to
reinstall (our app) or, if you're familiar with the settings in the
Registry, try to correct them yourself. For more information on the
Registry, click Help.

2. When opening certain reports she gets this error:

"The format specification for (control name) is invalid. You can't
save the output data to a file in this format until you correct the
settings for the format in the Windows Registry. Run setup to
reinstall (our app) or, if you're familiar with the settings in the
Registry, try to correct them yourself. For more information on the
Registry click Help."

3. In print preview

Clicks the icon to "output to the notepad". Get an error:

"The command or action ‘OutputToText' isn't available now. *You may
be in a read-only database or an unconverted database from an earlier
version of (our app). * The type of object the action applies to
isn't currently selected or isn't in the active view. Use only the
commands or macro actions that are currently available for this
database."

4. Publish w/ Excel and Publish w/ Word icons are greyed, cannot
output to Word or Excel, where before she could.

We have tested with an install of our app on WinXP Home Edition and
cannot recreate these problems.

We have run exhaustive searches on the error messages in Google and
the newsgroup, but can't find a solution.

I had her check registry setting for Report formats and Isam formats
and they appear to be normal for our installation.

I had her re-register mstext35.dll and msexcl35.dll as suggested in
posts with these errors.

We use Sagekey scripts for installation.

Does anyone have any suggestions about how to figure out what is wrong
here and how to fix it?

Thanks,
Kathryn

[Salad]

Kathryn Townsend wrote:

We have a customer using our Acc97 Runtime application on a Win 98
machine that was recently upgraded to WinXP Home Edition Service Pack
1. Shes states RAM is 228, CPU Pentium II 398 MHz , Hard drive 7.85
GB with 795 MB free space. Retail Access is NOT installed, Word and
Excel 9 ARE installed.

When first starting our app she got the message "Microsoft Acess can't
start because there is no license for it on this machine."
Check out MS KB Articles:

Q141373
Q191224

for a fix on that.

Maybe your user should reinstall and then fix that message if it
reappears.
We have run exhaustive searches on the error messages in Google and
the newsgroup, but can't find a solution.

I found the above at http://groups.google.com, advanced search, *Access*
in the newsgroup looking for "missing license".

See if the fixes for the license problem go away. Otherwise, try
uninstalling your app, uninstalling Ofice, reinstalling Office,
reinstalling your app and seeing if you get the license message and if so,
fix it.

One person at google, looking "setting for this format in the Windows
Registry" said "I ran into this probelm and found that my new computer was
set up to an incorrect server domain - may be worth a check."

Since the license problem deals with a FON file (Font?), it's possible
that will fix it.

[Kathryn Townsend]

Dear Salad,

My message clearly stated in the beginning that the LICENSE ISSUE WAS
RESOLVED. I put that in the message to give a history of the problem.
The problem we are having now is with formats. Please re-read my
message and if you have an appropriate response I'd love to hear it.

Thanks,
Kathryn

Salad <oi*@vinegar.com> wrote in message news:<40***************@vinegar.com>...

Kathryn Townsend wrote:

We have a customer using our Acc97 Runtime application on a Win 98
machine that was recently upgraded to WinXP Home Edition Service Pack
1. Shes states RAM is 228, CPU Pentium II 398 MHz , Hard drive 7.85
GB with 795 MB free space. Retail Access is NOT installed, Word and
Excel 9 ARE installed.

When first starting our app she got the message "Microsoft Acess can't
start because there is no license for it on this machine."

Check out MS KB Articles:

Q141373
Q191224

for a fix on that.

Maybe your user should reinstall and then fix that message if it
reappears.

We have run exhaustive searches on the error messages in Google and
the newsgroup, but can't find a solution.

I found the above at http://groups.google.com, advanced search, *Access*
in the newsgroup looking for "missing license".

See if the fixes for the license problem go away. Otherwise, try
uninstalling your app, uninstalling Ofice, reinstalling Office,
reinstalling your app and seeing if you get the license message and if so,
fix it.

One person at google, looking "setting for this format in the Windows
Registry" said "I ran into this probelm and found that my new computer was
set up to an incorrect server domain - may be worth a check."

Since the license problem deals with a FON file (Font?), it's possible
that will fix it.

[Salad]

Kathryn Townsend wrote:

Dear Salad,

My message clearly stated in the beginning that the LICENSE ISSUE WAS
RESOLVED. I put that in the message to give a history of the problem.
The problem we are having now is with formats. Please re-read my
message and if you have an appropriate response I'd love to hear it.

I did read it. And I did see that reinstalling XP solved the license probkem. But
who knows if the FON file is still screwing up your app. In order to know that you
'd have to have insider knowledge within Microsoft on their security issues, etc.

Debugging is not glamourous, sometimes tedious. For example, I may first uninstall
Office and your app, reinstall WinXP, then do a WindowsUpdate and do any&all
critical updates, then reinstall your app and see if there is a problem. If not,
reinstall Ofice and see if there is a problem.

Also, your errors, from what I saw on google, indicates this occurs when an update
to the OS or Ofice occurs and the people posted their problem but didn't get a
reply. You might want to send an e-mail to those folks and see if they ever
discovered the solution. The reason is that they may have gotten or found a
solution and continued on in life without going back to newsgroups and posting a
solution.

[Larry Linson]

Chastising a responder isn't a good way to continue the conversation,
Kathryn. Fortunately, Salad is much more considerate than some and did
continue. There are those who would not have. For other good suggestions on
effective use of the newsgroup, see the FAQ at
http://www.mvps.org/access/netiquette.htm.

Larry Linson

"Kathryn Townsend" <Kt***@WorkingArtist.com> wrote in message
news:a1**************************@posting.google.c om...

Dear Salad,

My message clearly stated in the beginning that the LICENSE ISSUE WAS
RESOLVED. I put that in the message to give a history of the problem.
The problem we are having now is with formats. Please re-read my
message and if you have an appropriate response I'd love to hear it.

Thanks,
Kathryn

Salad <oi*@vinegar.com> wrote in message

news:<40***************@vinegar.com>...

Kathryn Townsend wrote:

We have a customer using our Acc97 Runtime application on a Win 98
machine that was recently upgraded to WinXP Home Edition Service Pack
1. Shes states RAM is 228, CPU Pentium II 398 MHz , Hard drive 7.85
GB with 795 MB free space. Retail Access is NOT installed, Word and
Excel 9 ARE installed.

When first starting our app she got the message "Microsoft Acess can't
start because there is no license for it on this machine."

Check out MS KB Articles:

Q141373
Q191224

for a fix on that.

Maybe your user should reinstall and then fix that message if it
reappears.

We have run exhaustive searches on the error messages in Google and
the newsgroup, but can't find a solution.

I found the above at http://groups.google.com, advanced search, *Access*
in the newsgroup looking for "missing license".

See if the fixes for the license problem go away. Otherwise, try
uninstalling your app, uninstalling Ofice, reinstalling Office,
reinstalling your app and seeing if you get the license message and if so, fix it.

One person at google, looking "setting for this format in the Windows
Registry" said "I ran into this probelm and found that my new computer was set up to an incorrect server domain - may be worth a check."

Since the license problem deals with a FON file (Font?), it's possible
that will fix it.

[Kathryn Townsend]

Thanks for getting back to me. I'll have my customer try the Font
rename procedure and see if it changes anything. She didn't reinstall
XP, by the way, she reinstalled our application and that fixed the
license problem.

Glamorous, no. I've been working for two weeks remotely with this
customer just to get her to tell me the relevant system information
along with the error messages and a description of when she gets the
error messages and some diagnostic procedures. Its extremely tedious.

Answers I found in Google related to the error messages she is getting
suggested re-registering mstext35.dll and msexcl35.dll. She did that
and nothing changed. Other answers suggested that some registry
entries in the profile for the application were not correct. But I
had her check all of those and they appear to be normal.

So back to the Google drawing board.

Thanks again,
Kathryn

Salad <oi*@vinegar.com> wrote in message news:<40***************@vinegar.com>...

Kathryn Townsend wrote:

Dear Salad,

My message clearly stated in the beginning that the LICENSE ISSUE WAS
RESOLVED. I put that in the message to give a history of the problem.
The problem we are having now is with formats. Please re-read my
message and if you have an appropriate response I'd love to hear it.

I did read it. And I did see that reinstalling XP solved the license probkem. But
who knows if the FON file is still screwing up your app. In order to know that you
'd have to have insider knowledge within Microsoft on their security issues, etc.

Debugging is not glamourous, sometimes tedious. For example, I may first uninstall
Office and your app, reinstall WinXP, then do a WindowsUpdate and do any&all
critical updates, then reinstall your app and see if there is a problem. If not,
reinstall Ofice and see if there is a problem.

Also, your errors, from what I saw on google, indicates this occurs when an update
to the OS or Ofice occurs and the people posted their problem but didn't get a
reply. You might want to send an e-mail to those folks and see if they ever
discovered the solution. The reason is that they may have gotten or found a
solution and continued on in life without going back to newsgroups and posting a
solution.

[Salad]

Kathryn Townsend wrote:

Glamorous, no. I've been working for two weeks remotely with this
customer just to get her to tell me the relevant system information
along with the error messages and a description of when she gets the
error messages and some diagnostic procedures. Its extremely tedious.

Off topic. A program I use to work remotely on another person's computer is GotoMyPC (see
http://www.gotomypc.com) You connect to their computer over the web, it's similar to
PCAnywhere regarding features. It works quite well over dialup. Citrix thought enough of
the program that they purchased the company recently.

In case your "remotel support" is via phone, you may want your customer to check out
GotoMyPC. How it works is that she installs the GoToMyPC software on her computer. When
she wants you to visit her site, she sends you an e-mail invitation to enter her
computer. You hyperlink to the invitation site via your browser (Netscape works fine as
well as IE) and then you get connected to the user machine that sent the invitation.
With it you can be online, take over your customers computer and do whatever checks you
need to do or watch her do stuff on her PC. Chances are you know what to check and
rather than having the customer perform som action by issuing over the phone. You can
only access her computer via invitation so it is quite secure.

[Kathryn Townsend]

Hi Salad,

<<Off topic. A program I use to work remotely on another person's
computer is GotoMyPC (see http://www.gotomypc.com) You connect to
their computer over the web, it's similar to PCAnywhere regarding
features. It works quite well over dialup. Citrix thought enough of
the program that they purchased the company recently.>>

Yes, I'm familiar with these programs since my husband uses one to
connect to his PC as the office.

But back to the topic:

I've given my user instructions based on the article 141373 and hoping
she can do the procedure. Maybe simply removing and reinstalling
Office will do the trick. I'll let you know when I get an answer
back--probably in a few days.

Meantime, can someone explain to me how the process works for those
output formats/drivers? If the Acc 97 runtime app gets a message when
being opened related to formats not loaded, and Excel and Word icon
links are grayed in Print Preview (full error messages in my original
post), what is the function in Access or library dll that points to
the formats and/or registry settings and which registry settings are
being pointed to, or...? How is the connection made? Does anyone
know? I have searched for an answer to this, but I just must not be
asking the right question--

Thanks again for your help,
Kathryn