Does anyone know what type of trouble to expect with the conversion of

access97 to access2000.  I have a total of 20 databases with duplicate

gui screens one set for read the other for write.  What type of problems



should I expect?

Lateshia,



> Does anyone know what type of trouble to expect with the conversion of

> access97 to access2000.  I have a total of 20 databases with duplicate

> gui screens one set for read the other for write.  What type of problems

> should I expect?



Two problems I encountered were:



1) If you have macros which use menu items, some of the menu items may no 

longer exist.  Don't be surprised if some of your macros don't work.  

You'll have to remove the calls to extinct menu items and either: A) reset 

them to current menu items, or B) write modules if the new menu items 

don't exist for the task you want to do.



2) In modules, some items require the correct DAO library references.  

Access '97 uses 2.5.  Access XP (and I suspect 2000) uses 3.6.  Open any 

module and click TOOLS | REFERENCES to fix that.



Greg

Lateshia Daniels wrote:



> Does anyone know what type of trouble to expect with the conversion of

> access97 to access2000.  I have a total of 20 databases with duplicate

> gui screens one set for read the other for write.  What type of problems

> should I expect?



The only problems I encountered were that linking to several legacy 

Paradox for DOS tables got trickier and a control that did an ActiveX 

call to Crystal Reports would not work in an MDE. Microsoft naturally 

said they didn't know what Crystal Reports was doing, and Seagate said 

they didn't know what Access was doing. Searching on the second phrase 

of the error gibberish located an obscure article about MDE's and 

controls that modify printer parameters.



There is one other flakyness. Sometimes Access2000 says you haven't 

opened it exclusive when you did, and then it won't permit changes. 

Opening it shared will somehow get you exclusive use. Sort of a double 

negative becomes positive.



Paul

Just a couple things I have seen:

   *  Access2000 is Unicode support throughout, so the database gets 

larger by as much as 70% (sometimes less).  The use of Unicode is a huge 

benefit is you suppport International languages as the old code page 

strategy was more complicated.

   *  If you convert using DAO's .CompactDatabase command 

(programmatically) instead of manually, Access still barks at you that 

thbe database has not been converted, even though it has.  There is a 

Microsoft Q bulletin about this but I don't recall the number.



R



 

> Does anyone know what type of trouble to expect with the conversion of

> access97 to access2000.  I have a total of 20 databases with duplicate

> gui screens one set for read the other for write.  What type of problems

> 

> should I expect?

>