G
Guest
I had OfficePro97 running just fine (WinXP Pro SP2), with a nice little
Access97DB, which I loaded up on my ISP's server. Then I installed Access
2003 (which required uninstalling Access97 - sigh). Of course, Access 2003
wanted to try to convert the 97DB, which to get around the "read-only" issue
I was required to allow. Then I exported the "new" DB as an Access 97 DB, and
uploaded it back to the server. Now the server is heaving up when I try to
connect to this DB (on the web server).
I want to explore the possibility that Access 2003's "export to 97" isn't
101% accurate (hey, it happens...). So I got out my Access2003 CD and did a
Remove, then dug out my OffPro97 CD and re-installed Access 97.
Ah, but when I try to run Access 97, I get a terse dialogue explaining that
"Microsoft Access can't start because there is no license for it on this
machine." Ahem.
So I believe that Access2003 is not "completely removed". Sounds right?
Otherwise Access97 should start up without such a problem, as it did prior
to installing Access 2003.
Access97DB, which I loaded up on my ISP's server. Then I installed Access
2003 (which required uninstalling Access97 - sigh). Of course, Access 2003
wanted to try to convert the 97DB, which to get around the "read-only" issue
I was required to allow. Then I exported the "new" DB as an Access 97 DB, and
uploaded it back to the server. Now the server is heaving up when I try to
connect to this DB (on the web server).
I want to explore the possibility that Access 2003's "export to 97" isn't
101% accurate (hey, it happens...). So I got out my Access2003 CD and did a
Remove, then dug out my OffPro97 CD and re-installed Access 97.
Ah, but when I try to run Access 97, I get a terse dialogue explaining that
"Microsoft Access can't start because there is no license for it on this
machine." Ahem.
So I believe that Access2003 is not "completely removed". Sounds right?
Otherwise Access97 should start up without such a problem, as it did prior
to installing Access 2003.