GREAT GOOGELY MOOGELY 97-2000

[Smack]

I was just informed by my IT manager that I have less than one month to convert all active access databases (7)from A97 to A2000. I have not even seen 2000 yet! What type of conversion process is involved? I will be getting a laptop with 2000 on it to work back and forth with some beta conversions. What type of problems did y'all encounter (if any) when making this transition? Any tips, tricks or areas of potential disaster I should be aware of? All info, as always, will be greatly appreciated.
-Smack >:0>

Self-development is a higher duty than self-sacrifice.
-Elizabeth Cady Stanton

 

[atadbitslow]

I was just about to post this same question--I'm having trouble just "opening" an Access 97 database in 2000. I get error messages about loading certain forms and then I get a message box that says "The Visual Basic for Applications" project in the database is corrupt." I got the same errors when I tried importing all the forms etc.

What is the easiest relatively problem-free way to convert?? I don't want to have to re-create all my forms!!

Thanks!

 

[Smack]

Okay, I'm starting to get a little panicky. All information will be grewatly appreciated.
-Smack

 

[THoey]

Smack,

I have not done this myself, but I have heard that it is a bit of a pain. There is a conversion tool, but you have to recompile all of your code and forms and verify that it recompiled correctly. The biggest thing I have heard is people having problems with DAO to ADO or ADO to DAO conversion. The only two things I can suggest is that you back up first and do a keyword search here for Access 2000 in the title of the thread. That should get you some tips...

As always, any specific problems, repost here and someone will be able to help. Terry M. Hoey
th3856@txmail.sbc.com
While I don't mind e-mail messages, please post all questions in these forums for the benefit of all members.

 

[Smack]

I did a search and looked though numerous threads and did not find anything.
-Smack
>:O>

 

[MichaelRed]

Hmmmmmmmmmmmmmm,

Introduce the "boss" to reality programming?

Perhaps, you could make up a chart (in Access '97?). Shows the # '97 mdb's vs time. Another could take this ratio and plot the % time spent on work vs searching for a new 'opprotunity' vs the deviation from the first track?

Count the number of lines of code and divide by the hours remaining till the deadline. Ask the "boss" (and yourself?) "Is this reasonable?, Possible?" Go forth and make YOUR decision.


MichaelRed
redmsp@erols.com

There is never time to do it right but there is always time to do it over

 

[Smack]

Unfortunately I work in one of nine north american business units. Corporate say's we must change all BU's to windows 2000. No options, no choices. Can we continue to use our A97 with the 2000 operating system? I was not told A97 specifically had to change, only that the IT mngr has to upgrade all BU pc's to 2000.
-Smack B-(

 

[smiley0q0]

smack what is your email address, i might have something you will want. you can either email me at jared_taylor@associatescommerce.com or post it here.

 

[Rohdem]

OK, take a deep breath.......

Access 97 will work with Windows 2000......

but there are some issues with database corruption in large databases with a high number of users. However, Access 2000 will not solve this problem. We had some trouble with this in a split database with 20+ users and a size of about 25 meg (back end) running a mixture of Win 95,98, NT, and 2000. Microsoft is working on this problem and I believe the next service release for Win 2000 is supposed to fix the problem.

As far as converting goes, Terry is right about the ADO vs. DAO issues. If you are going to go ahead and convert these databases, you will need to research this thoroughly before you start. Mike Rohde
rohdem@marshallengines.com

 

[Smack]

I am not a programmer, so other than a few helpful codes from Tek-tips, everything is done with basic tools. What's behind everthing I've created? I sure don't know!!
-Smack

 

[MichaelRed]

If it is ' ... all basic tools ..." the conversion should be a lot easier. But not trouble free. If they work as '97 under Win 2K, then migrate them at a MUCH slower pace and save yourself a ton of stress / worry. Biggest issue I know of is the DAO/ADO, but even here, you can start with just maaking sure that ALL of hte db and recordset declatations use DAO initally and then do the long term conversion to ADO one at a time.


MichaelRed
redmsp@erols.com

There is never time to do it right but there is always time to do it over

 

[Smack]

I could not find ADO in help or my bible, I saw DAO in help, but did not really understandwhere it was going, it listed the basic schematic, but, well, hmmm, could somoene give me a simple explanation?
-Smack

 

[Francescina]

I converted dozens of A97 applications to A2K and I can confirm that the conversion will be successful in no time if:

1.) The A97-modules are error-free.
2.) You do not use "alien" OCX files, libraries or automation in A97
3.) You de-activate the security system in A97 before
4.) If you activate the DAO3.6 reference once you opened your freshly converted application.

If you have more specific questions, you can also send me a direct e-mail: msACCESSteam@Hotmail.com.

 

[DK77]

Hello all,

I'm in the same boat as Smack, and I took the "quick and dirty/fine tune later" approach suggested by MichaelRed.

I'm reading up on ADO but all of my databases were built using DAO techniques. After converting my databases to Access 2000, I simply removed the reference to ADO 2.5 and added a reference to DAO 3.5. They run fine.

Now my major gripe with Access 2000 is the Help files. They have been gutted of all the detailed information on DAO methods & properties. In fact a lot of the non-DAO help subjects have been "horribly foreshortened" as concerns intrinsic constants, arguments, methods, code examples, etc. My last option is always "Search the Web for more information on...", which doesn't send me to a Microsoft site as one might expect, just "out there" onto the Internet. I've got DAO reference books on my desk but I sure wish this information was still available in Access itself.

Is there some way to add this information back into the help files?

 

[nberryman]

Check the Microsoft knowledge base for Conversion info, there's quite a bit there.

One thing that may help is to compile your code in 97, there may be some left over unused code in it. If it doesn't compile in 97 it won't convert to 2000


Good luck!!!!!


Neil Berryman
IT Trainer
neil_berryman@btopenworld.com

 

[LittleSmudge]

Elizabeth,
What sort of contract are you on?

Does your IT manager realise that with that sort of experience under your belt your open market value has just jumped significantly ?



In reality you best learning method is to try it out ( learn by doing ) and visiting here regularly.

Recomplile existing Database
Remove Security
Open in Access 2k
Activate the DAO3.6 reference library in A2k
Test
(Remember that any user wanting to run the new database on A2k will need to activate DAO3.6 on THEIR copy of Access as well.)

Once the panic is over you will benefit from going back and converting all the DAO code to ADO so that you can get rid of the DAO3.6 reference library - which will make running the A2k databases easier on new instalations of Access



See you soon.

G LS

 

[petermeachem]

I agree with Francescina. I've converted quite a few with no problems at all. Just open them in Access 2000 and it will do it for you. Not had a problem.

Mind you, I think 97 is much much better than 2000. Peter Meachem
peter@accuflight.com

 

[Rhonin]

One other note of interest....
We have a rather large number of users that use their own in-house apps and I get alot of calls from them concerning errors on conversion.
Almost all have fallen into two categories:

A: they did not click the DAO (3.5 or 3.6) reference

B: There was all kinds of left over code from controls/buttons that had been deleted. (button deleted, code still their)

Irregardless what you plan for, something will come up to cause further stress.
Looking forward to your next Q.

Rhonin
"too many questions, too little time..."