Does anyone know of any VBA 'gotchas' when moving code from Excel 2k to XP? Stuff like needing to explicitly set ScreenUpdating back on etc. We have to test about a hundred different spreadsheet systems before the business can upgrade to XP, and if we can do a search and fix in the code before getting the users to test functionality it would make our lives much easier.

Cheers,

Chris


There are two secrets to success in this world:
1. Never tell everything you know

__________________
There are two secrets to success in this world:
1. Never tell everything you know

chrislepingwell,

Despite the criticism and rumors -- Microsoft does an excellent job of getting it right when it comes to compatibility.

I have a Windows 2k system at work and Windows XP at home. I keep the two systems in sync and am transferring Excel files back and forth on a daily basis (i.e., using zip disks and an excellent program called SynchronX).

The only problem I've ever had was that I once used a command that was available in XP (a FileSearch command of some kind) which wasn't yet available in 2K -- but that's to be expected.

CarlR