vba access 97 -> access 2000 
Author Message
 vba access 97 -> access 2000

One of my customer want to upgrade their computer to Windows 2000 and
office 2000 but for now he have an application using VBA access 97 do
i need to be fear about this upgrade for this application ?
Alain Demers
Directeur, exploitation
Vision INTERNET DICI inc.
http://www.*-*-*.com/
(514) 355-7235


Tue, 03 Jun 2003 02:58:31 GMT  
 vba access 97 -> access 2000
In general, I've seen small apps convert just fine.  However, if he's running a
large system (Access based account, etc.) which may have a lot of code, hundreds
of objects, etc. then I would expect to have some issues, and you'd better have
an access developer handy to assist.

I've seen apps convert cleanly, and I've seen apps require weeks of tweaking and
modification. You best bet would be to test it first.  And, if it's a large app,
don't forget to recompile it, etc.

Quote:
-----Original Message-----

One of my customer want to upgrade their computer to Windows 2000 and
office 2000 but for now he have an application using VBA access 97 do
i need to be fear about this upgrade for this application ?
Alain Demers
Directeur, exploitation
Vision INTERNET DICI inc.
http://www.dici.qc.ca
(514) 355-7235
.



Wed, 04 Jun 2003 06:05:49 GMT  
 vba access 97 -> access 2000
Perhaps you can convince them to use A97 still. (A2K has lots of bugs.)
This is the short version of how to install A97 on a PC w/ A2K already
installed:

I recently needed to install Access97 on a PC with A2k already installed.
I looked in the MSKB and it has a fairly simple page explaining how to do
it.

1. Re-name Msaccess.exe to msaccess.a2k (or anything else)
2. Re-name hatten.ttf to hatten.sav (or anything else)
3. Install A97 in a separate directory: C:\program files\microsoft office97
4. Delete the hatten.ttf file with the older date and smaller size and
change hatten.sav back to hatten.ttf.
5. Change msaccess.a2k back to msaccess.exe.

The only "problem" was the slow response when changing between versions of
Access.
This must be the Registry key re-writing that Michka refers to.

--
Joe
Access MVP
Check out Dev Ashish's web site for answers to common questions
http://www.mvps.org/access/


In general, I've seen small apps convert just fine.  However, if he's
running a
large system (Access based account, etc.) which may have a lot of code,
hundreds
of objects, etc. then I would expect to have some issues, and you'd better
have
an access developer handy to assist.

I've seen apps convert cleanly, and I've seen apps require weeks of tweaking
and
modification. You best bet would be to test it first.  And, if it's a large
app,
don't forget to recompile it, etc.

Quote:
-----Original Message-----

One of my customer want to upgrade their computer to Windows 2000 and
office 2000 but for now he have an application using VBA access 97 do
i need to be fear about this upgrade for this application ?
Alain Demers
Directeur, exploitation
Vision INTERNET DICI inc.
http://www.dici.qc.ca
(514) 355-7235
.



Thu, 05 Jun 2003 12:37:07 GMT  
 
 [ 3 post ] 

 Relevant Pages 

1. VBA OpenDatabase: Access 97 <-> Access 2000

2. Access 2000 VBA Handbook vis a vis Access 97 VBA Handbook

3. Access 97 -> Access 2000 VB Scope Problem

4. Access 97 ---> Access 2000 migration

5. access 97 -> access 2000

6. Access 97 VBA modifications not visible in Access 2000

7. Using VBA to Convert Access 2000 database to Access 97

8. Converting Access 97 to Access 2000 via VBA

9. Access 97 upgrade to Access 2000 or Access 2002

10. ACCESS 97->2000: exclusive open??

11. ADO: Convert Access 97 -> 2000

12. Access 97->2000 HELP PLZ.

 

 
Powered by phpBB® Forum Software