What problems can I expect when my company shifts from NT2000 to 32-bit Vista and Office 2003?
Question:
Their continued working is essential to keep us in "production" mode. They all run fine on NT2000 networks and current XP systems, and on software running the gamut up to Office 2003.
Questions - What kind of problems should we be looking for when the transition takes place? What types of operations in the old applications cause grief after conversion and how so? Can the new software's security programming screw things up?
We want to do some pre-changeover program testing in advance of the "upgrade". We are trying to get an idea what elements of our software might blow up in our faces and have to be debugged, "re-tooled", or re-programmed. Any feedback would help us think about how much time and effort ($$$'s!) we might spend doing this
Answer:
Going up to Vista is causing a lot of headaches for companies. This is due to the new administration set up that Vista has. Vista pretty much asks every time some application tries to do somethig, Vista asks the user to clear it. This is all right in theory but the fact is that not every one knows what some of these right issues is about and if they click the wrong button, Vista makes it very difficult to bring it back to normal.
Another thing is that Vista is new and a lot of drivers and set up commands are not up to prime moment. So I have heard a lot fo macros and programs while working in XP suddenly start freaking out in Vista.
When you guys upgrade make sure you are ready. If you guys are doing this yourselves, the testing might take anywhere from couple of weeks to months depending how fast you guys can do it. Money wise it should be too bad, time will be the bigger factor. Consulting services will speed it up but truth be told you guys should need it, its not that bad either. Just go through your programs randomly depending on date made and try transferring them to a vista machine and see how it goes.
http://www.carbonfrost.com/
More Questions & Answers...