2000 and 97

[bookouri]

I have a large number of Access97 databases in a network environment of about 200 users with 97 runtime installed. I just got a new machine that came with Office 2000 Pro/Windows 2000 installed. Can I install Access97 and run both versions from my workstation so I can continue to support the 97 databases? What version of Office 2000 do you have to upgrade to to get Office 2000 runtime so I can upgrade the entire system? Can I use Access2000 to manage/develope Access97 databases?

Any suggestions would be appreciated...

 

[hennep]

You can install Access 2000 on the same machine however,
A2K takes over the association of the mdb files when it is installed and EVERY TIME it is started. To "WorkAround" this problem you need to make shortcuts for all the A97 applications you want to maintain.

 

[RickSpr]

Alternatively, you can just keep a shortcut directly to the A97 msaccess.exe. Whichever one you opened last--A2K or A97--will be the one that opens when you click on a database. If the wrong one opens, you'll get a message (either about the database being in an unrecognized format, or about converting it to A2K). You can then just exit and use the shortcut to the .exe.

Note: I think you'll probably have to install A97 and then reinstall A2K in order to run both. You might even have to uninstall A2K first. Rick Sprague

 

[bookouri]

i actually found a microsoft tech doc that explained the convoluted way to install 97 after 2000 is already installed. Have both running now seemingly without problems. Does anyone know if i can work in 2000 and save changes as 97 or do i have to use 97 for development still?

I really need to get up to 2000 runtime, but even the microsoft site is confusing about what version you actually have to upgrade to to get runtime..

 

[RickSpr]

I use a dual 97 and 2000 development box. You're supposed to be able to save 2000 as 97, but I've never depended on it; I just maintain 97 databases with 97. Keeps me from using VBA statements and objects that aren't supported in 97. Rick Sprague

 

[LeoAssetMan]

I have Office 2000 running. Also I followed MS instructions and installed just MS Access 97 on the machine with Win98. When I installed Access 97 I used Custom install and installed all features. Both 2000 and 97 are working fine. My dilemma is that I need to import Excel table into 97 and it doesn't show the Excel format.

By some reason it says "Not all file types are installed be default". So system thinks I did a default installation.

Please HELP !

 

[ronleclair]

I have a related issue with A97 and A2K. I have an application that is shared to multiple users. It is a A97 application and up until now, all the users had A97. Slowly, some of the users are being upgraded to A2K. So, now we have users with A2K and A97 accessing the A97 database at the same time.

Here is the issue. If the A97 users are already in the database, the A2K users cannot access the database because it is already open. Solutions at that point would be to have the A97 users close and have the A2K users open first in order to 'convert' the database. This then allows all users to get in no problem. Even the A2K users can close the application and then open it no problem. (Unless they log off, thus resetting their session variables.)

Is there some way to allow the A2K users to open the application when A97 users are already in the application without having to make the A97 users close out first??

 

[FunkyMonkey]

on the issue of having to update Access 97 and 2000 appications, I hope this may help somebody....

On my pc I run A2K. I have applications that I share with other users, running A97.

I would first make the application in A2K, then split the database, and saved the back end tables database in 97 format. Convert the A2k Front end to A97 that is then distributed, having both application versions reading from the same data source.

When I need to make a change to the structure of the database, I make the change in A2k, convert to A97 format, then overwrite the existing A97 db with the new version.

Hope this helps...

J

NB. I tried to execute this same procedure on another application which uses unix output text files as the source data. My macros that do the work only import to the native application, not the back end tables that I want updated and I do not have the technical know-how to import data into a separate database. Can anyone help me on this one? Is it possible without heavy-duty coding?

Thanks

 

[MontyBurns]

Hi,

I'm looking after loads of A97 DBs, some of which I've developed but most of which are simpler (but messy!) DBs which I just administer.

We're upgrading to Win2K and A2K in the next couple of months. We will probably have quite a while when users are mixed between 97 and 2K.

If I convert them all to client-server apps, will I be able to connect both 97 and 2K front ends to the 97 backends? Are there any gotchas/pitfalls I should look out for?

Thanks,
Burns

 

[FunkyMonkey]

On the networks we are currently running, occasional errors occur when the front end in 2000 cannot find certain tables in the 97 back end. It is sporadic, and I have yet to find a pattern that I can repeat.

To rectify the situation I delete the 'ghost' table in 2000 (with the little linked arrow beside the table symbol), and re-link it, whenceforth it should work as it should have in the first place. Whether this peculiarity is something unique to our network or to this kind of application utility is something I cannot comment on. Apart from that, I have not experienced any other major pitfalls with using 97 & 2000 in this way.

Best of luck, Monty!

 

[MontyBurns]

cheers Funky