Migrating from 97 to XP

[sxux]

All,

I have several Access 97 applications which were running on NT systems. Now because of corporate policy change, all of the users in my company are getting Windows XP machines. So make the applns run in XP i have used the convert database option ,that pops up when we try to open a previous version (97) of access db in office 2002. But the problem is that the applications are real slow. I need to address this issue as soon as possible.

Any suggestions/ideas will greatly appreciated.

Thanx in Advance

 

[dakota81]

Access '97 is compatible under Windows XP... Just because Office XP & Windows XP share the same naming conventions doesn't mean they're a match made in heaven...

Seriously, were I work we have Access '97 database files and everyone is running Access '97 except for one which has Access 2002. We keep the file format for this computer as Access '97 instead of converting to 2000 or 2002 format.

There is no noticable system performance differences between Access 2002 running a '97 file and Access '97 running that same file.

Just checking, when you're testing the performance, you don't have two copies of Access open, right? Because on any system that will make doing anything within the application down to a painful crawl.

So my question is, are the new machines up to par with Window's XP's uber-great system requirements? Or maybe have you tried not converting the applications to 2002 format, leaving them as '97?

 

[dakota81]

and oh, my experience w/ Access 2002, to leave the file in '97 format, we have to select the "leave in '97..." option then click "OK" or "OPEN" (I'm not near the computer @ the moment). Then that window pops up a second time and that's when we click "CANCEL" then the database opens up.

Do not ask me why our's runs like that, it just does. But thankfully we only have to do that once (next time you open up the file, it goes straight in).

 

[Kraeg]

sxux, are they all (97 and XP databases) accessing a 97 backend? That could explain the speed issue.... last year I set up a fronted/backend system, with a mix of 97/XP frontends and a 97 backend on the server; it was slow, and the backend became corrupted easily (once a week).
They finally finished upgrading to Office XP (over time) and now it works a lot faster, and no corruption, which I can only put down to it now being all XP frontends and an XP backend.

 

[sxux]

All,

I guess i missed some points while i posted my scenario. Our users have a mix of Windows XP and Windows NT operation systems. All of them access and need to update data in a central location. Originally before any changes were done to the front end /back end , it was all NT systems with access 97.
To address this we have now moved the backend to Oracle,a nd using linked tables in access. Access is just our front end now. The front end appln is put in a network share. we are supporting 2 versions of access, 1) native 97 version and another Access 2002 version ( obtained by using convert option). Both these versions are kept on the network share. so NT users will access 97access.exe and XP users use 2002acess.exe. This we have done to prevent XP users from converting accidentally the version being used by 97 users.

The problem, as i described in my earlier post, is that for XP the user experience is real slow.

Does starting a blank project in XP and importing all objects from 97 version help? ( without converting from 97). As i understand in my company it is going to take some time before everyone is moved to XP. until that time i need to support both NT and XP.

Any help greatly appreciated.

Thanks
Sxux