Access97 conversion issues


A

Advance Scout

I want to upgrade my computer and get windows 7. I have been told
access97 will not run on windows7 without converting to later access so
here is what I have done to start the conversion process...

I had an old copy of office xp (access 2002) that I never used... and
installed it on a secondary computer system - so I dont screw up any of
my main access files. This was to test everything I am doing to the
conversion before I actually do it. I used custom install and now have
both access 97 and access 2002 on my secondary machine. I copied the
mdb file to the secondary machine.

Using this secondary system, I opened my access application and it asked
if I wanted to convert the file to access 2002. I received error
message that there were compilation errors during the conversion process
and that the database was not saved in compiled form. It also said it
would have to recompile each time it opens.

The application is running fine. I checked the conversion error log and
it said error loading activex controls on two forms (activx ctr 83 and 6).

1. If I remove these ctrls from the forms will that solve the conversion
problem? Is it not worth bothering with and just let it recompile each
time? Why wouldnt these controls work and can I fix the controls so
they do work?

2. Will this new access 2002 now work on windows 7?

Once I get the bugs worked out I will then duplicate the procedure on my
main access program and machine.
 
Ad

Advertisements

A

Advance Scout

as a test I just deleted both forms in question (they are unused forms)
and I still had a conversion error (which was also on the original
conversion error log) in a module. Thats all the conversion log
indicated was "module" but with no module name. So I went into my module
tab and, one at a time I deleted each module to find the problem module,
and then ran the conversion process again. Even after deleting EVERY
module I still get a "module" conversion error when converting. Any ideas?
 
J

John Spencer

Did you check the references in VBA?

Open the VBA window
Select Tools: References from the menu
Uncheck any references that are marked as MISSING
Uncheck any references that you don't need.

John Spencer
Access MVP 2002-2005, 2007-2010
The Hilltop Institute
University of Maryland Baltimore County
 
T

Tony Toews

I want to upgrade my computer and get windows 7. I have been told
access97 will not run on windows7 without converting to later access so
here is what I have done to start the conversion process...

A97 will run on Windows 7. Now you need to run it as administrator
which isn't the best idea of course but it does run. Now if your on
a corporate network and you don't have admni priviliges then yes this
is a problem.

Tony
--
Tony Toews, Microsoft Access MVP
Tony's Main MS Access pages - http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
For a convenient utility to keep your users FEs and other files
updated see http://www.autofeupdater.com/
 
A

Advance Scout

wow- I was told it only works on windows7 if its in some type of xp
emulation mode and only using win7 professional ...and only if you had
the right CPU. (lots of different "and only's")

if I can run it as administrator and it works- you said that its not the
"best idea"- why? I am the only user (well... occasionally my wife but
thats ok )- are there any issues running as admin that I am not aware of?
 
A

Advance Scout

No problems with references that I see- but then I went and tried
compiling a test copy of the working Access 97 program and had a batch
of class module errors in 4 different reports when I compiled (about 8).
I guess I was running a non compiled program all these years.. with
no ill effects. Anyway I deleted these 8 errors from my test copy as
well as two additional forms that were also in the conversion problem
logs and the program compiled perfectly. Then I opened the program in
Access 2002 and it converted over perfectly. A test run of the program
seems to show it working correctly.


So now i guess (hope) I can use windows 7 once I compile and convert
the real access 97 application?
 
Ad

Advertisements

D

Douglas J Steele

I'm not aware of any issues.

Note that you can create a shortcut pointing to msaccess.exe, and set that
shortcut so it always runs As Administrator. (It's an option when you click
the Advanced button on the Shortcut tab of the shortcut's properties) You'll
still be prompted by UAC, but at least you won't always have to remember to
start it As Administrator.

"Advance Scout" wrote in message


wow- I was told it only works on windows7 if its in some type of xp
emulation mode and only using win7 professional ...and only if you had
the right CPU. (lots of different "and only's")

if I can run it as administrator and it works- you said that its not the
"best idea"- why? I am the only user (well... occasionally my wife but
thats ok )- are there any issues running as admin that I am not aware of?
 
A

Advance Scout

As it turns out I finally compiled and converted access 97 to access
2002, without errors, so I think my problem is solved anyway - or am I
forgetting something?
 
T

Tony Toews

As it turns out I finally compiled and converted access 97 to access
2002, without errors, so I think my problem is solved anyway - or am I
forgetting something?

If it works for a year or two then you haven't forgotten too much.
<smile>

Tony
--
Tony Toews, Microsoft Access MVP
Tony's Main MS Access pages - http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
For a convenient utility to keep your users FEs and other files
updated see http://www.autofeupdater.com/
 
T

Tony Toews

wow- I was told it only works on windows7 if its in some type of xp
emulation mode and only using win7 professional ...and only if you had
the right CPU. (lots of different "and only's")

I do have the Win XP emulation, whatever it's exact name is, installed
but I'm not using it. Dunno what that person means by right CPU.
if I can run it as administrator and it works- you said that its not the
"best idea"- why? I am the only user (well... occasionally my wife but
thats ok )- are there any issues running as admin that I am not aware of?

The problem with running as admin, if you are distributing your apps
to other people, is that you might do something in your code that only
an admin should do. Then when regular users run the app it will fail
on them.

Tony
--
Tony Toews, Microsoft Access MVP
Tony's Main MS Access pages - http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
For a convenient utility to keep your users FEs and other files
updated see http://www.autofeupdater.com/
 
Ad

Advertisements

D

David-W-Fenton

The problem with running as admin, if you are distributing your
apps to other people, is that you might do something in your code
that only an admin should do. Then when regular users run the app
it will fail on them.

But if A97 will only run as admin, then that's not really an issue,
since the app wouldn't be runnable in A97 except with the necessary
permissions.

I would say that there is really no risk in running an A97 app as an
admin in Vista/Win7.
 
Ad

Advertisements


Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top