Access 97 to 2003 conversion - modules not copied across

[Roy Tong]

I maintain a shared database on Access 97. I've just tried converting
a test copy of the database to 2003 and it appeared to work OK. That
is I got no error messages. However then I look at my modules, only 2
out of 9 have copied across.

Do I need to do something special to recompile modules and take them
across to the new version? I thought the conversion process would just
handle it. Well it seems to for 2 of the 9 and I got no indication of
any failure.

Any constructive advice will be gratefully received.

Thanks,

Roy

[Tom van Stiphout]

On Mon, 10 Sep 2007 03:41:07 -0700, Roy Tong <ro*****@hsbc.comwrote:

I don't know why it failed, but since it's only a few tables you could
import them manually using File Get External Data Import

-Tom.

>I maintain a shared database on Access 97. I've just tried converting
a test copy of the database to 2003 and it appeared to work OK. That
is I got no error messages. However then I look at my modules, only 2
out of 9 have copied across.

Do I need to do something special to recompile modules and take them
across to the new version? I thought the conversion process would just
handle it. Well it seems to for 2 of the 9 and I got no indication of
any failure.

Any constructive advice will be gratefully received.

Thanks,

Roy

[Allen Browne]

It ought the work the way you expect, Roy, so something else is going on. It
might be the kind of problem that a decompile might fix.

1. Make a backup of your A97 MDB (in case something goes wrong.)

2. Using A97, compact the database to get rid of any old stuff:
Tools | Database Utilities | Compact/Repair

3. Close Access. Decompile the database by entering something like this at
the command prompt while Access is not running. It is all one line, and
include the quotes:
"c:\Program Files\Microsoft office\office\msaccess.exe" /decompile
"c:\MyPath\MyDatabase.mdb"
(Note: use the path to Access 97.)

4. Compact again.

5. Open a code window.
Choose References from the Tools menu.
Uncheck any references you do not need.
For a list of the ones you typically need in your version of Access, see:
http://allenbrowne.com/ser-38.html

6. Still in the code window, choose Compile from the Debug menu.
Fix any errors, and repeat until it compiles okay.

7. Try the conversion again.

If you are totally stuck, you can copy'n'paste from the old modules into new
modules in A2003, but that should not be necessary.

For other things you might need to be aware of, see:
Converting from Access 97
at:
http://allenbrowne.com/ser-48.html

--
Allen Browne - Microsoft MVP. Perth, Western Australia
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"Roy Tong" <ro*****@hsbc.comwrote in message
news:11**********************@19g2000hsx.googlegro ups.com...

>I maintain a shared database on Access 97. I've just tried converting
a test copy of the database to 2003 and it appeared to work OK. That
is I got no error messages. However then I look at my modules, only 2
out of 9 have copied across.

Do I need to do something special to recompile modules and take them
across to the new version? I thought the conversion process would just
handle it. Well it seems to for 2 of the 9 and I got no indication of
any failure.

Any constructive advice will be gratefully received.

Thanks,

Roy

[Roy Tong]

On Sep 10, 2:40 pm, "Allen Browne" <[e-mail]:

It ought the work the way you expect, Roy, so something else is going on. It
might be the kind of problem that a decompile might fix.

1. Make a backup of your A97 MDB (in case something goes wrong.)

2. Using A97, compact the database to get rid of any old stuff:
Tools | Database Utilities | Compact/Repair

3. Close Access. Decompile the database by entering something like this at
the command prompt while Access is not running. It is all one line, and
include the quotes:
"c:\Program Files\Microsoft office\office\msaccess.exe" /decompile
"c:\MyPath\MyDatabase.mdb"
(Note: use the path to Access 97.)

4. Compact again.

5. Open a code window.
Choose References from the Tools menu.
Uncheck any references you do not need.
For a list of the ones you typically need in your version of Access, see:
http://allenbrowne.com/ser-38.html

6. Still in the code window, choose Compile from the Debug menu.
Fix any errors, and repeat until it compiles okay.

7. Try the conversion again.

If you are totally stuck, you can copy'n'paste from the old modules into new
modules in A2003, but that should not be necessary.

For other things you might need to be aware of, see:
Converting from Access 97
at:
http://allenbrowne.com/ser-48.html

--
Allen Browne - Microsoft MVP. Perth, Western Australia
Tips for Access users -http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"Roy Tong" <[e-mail] in message

news:11**********************@19g2000hsx.googlegro ups.com...

I maintain a shared database on Access 97. I've just tried converting
a test copy of the database to 2003 and it appeared to work OK. That
is I got no error messages. However then I look at my modules, only 2
out of 9 have copied across.

Do I need to do something special to recompile modules and take them
across to the new version? I thought the conversion process would just
handle it. Well it seems to for 2 of the 9 and I got no indication of
any failure.

Any constructive advice will be gratefully received.

Thanks,

Roy- Hide quoted text -

- Show quoted text -

Allen,

Thanks for the prompt response. On looking further, if I open the pre-
converted database under Access 2003 I can see only 2 modules so it's
no wonder the missing 7 modules don't appear in the converted
database. However if I open the preconverted database under Access 97
I can still see all 9 modules. My lack of familiarity with Access 2003
is letting me down here but I'll do some further investigation and
follow up the points you raised.

Thanks again,

Roy