Issues with migration from NT to XP?

[easyit]

Hi,

We are about to migrate from NT to XP. There are a few hundred Access db's all A2k. Under XP we still will be using office200 and A2k.

I know that I have two issues that I need to tackle with this, that is the library references that will be different and file locations that might be different.

But, beside these I am wondering if there are other things that might pop-up. Does anybody have ideas, or experience with this?

EasyIT

 

[Ed2020]

My company is going through a similar upgrade process at the moment (we're moving from NT4 to XPP, Access 97 and 2000 to Access 2003).

The problems I've encountered so far are:

1. Different versions and locations of DLL files.
2. Differences in certain Environment Variables (although your IS people should be able to sort this out fairly easily).
3. Access 2003's insistance on displaying *many* security warnings every time you open a database, although this is an annoyance more than anything else.

Other than that the conversion programme has been pretty painless. Access2002 and 2003 seem to work fine with Access 2000 databases.

Ed Metcalfe.

Please do not feed the trolls.....

 

[PCLewis]

And have you noticed performance hits in ODBC calls across the LAN or WAN after moving from Win2k to XP?

My experience with only one application that was coded in something like Access (whatever the first was!) then migrated to Access2, then to 97, then to 2000, by as many developers... My biggest problem was that everything was being done "the hard way" and in order to keep my sanity when looking at the code I had to rewrite most of it...

All in all though, even a bad app like the one I had to make sense of migrated smoothly and worked straight away.

 

[Ed2020]

PCLewis,

No, I haven't noticed any ODBC performance degradation. Is this a common issue then?

Taking on other peoples' work has always been one of my biggest headaches too. Still, keeps like interesting!

Ed Metcalfe.

Please do not feed the trolls.....

 

[PCLewis]

http://www.tek-tips.com/viewthread.cfm?qid=1086592&page=1

http://snakefoot.fateback.com/tweak/winnt/network.html

http://support.microsoft.com/kb/Q815230

These are the links I found when I had an issue with performance. I do not know how common it is but another recent topic on this site:

http://www.tek-tips.com/viewthread.cfm?qid=1121644&page=1

indicates that performance issues when moving to XP can happen. All of the info in the links boil down to: Microsoft changed a default setting in the network driver in XP so that potentially, on networks where bandwidth is no issue, additional latency is added to some forms of traffic. In my case, the back end was Oracle and due to damn stupid internal company policy / issues I have not been able to get an affected workstation updated to XP SP2 in order to see if it helps

 

[Ed2020]

PC,

Thanks for the info. I wasn't aware of this issue before.

Ed Metcalfe.

Please do not feed the trolls.....

 

[easyit]

Hi Everybody,

Thank you all so far for your input. I hadn't expected performance to be an issue, since migration from NT to XP seems to be a step forward...

EasyIT

 

[Ed2020]

Never assume that later versions of MS software are a step forward.

Ed Metcalfe.

Please do not feed the trolls.....