Updating to Office 2010

**northernladuk** · 12 June 2012, 10:16

Originally posted by NickNick View Post

So ClientCo is migrating from an old version of Office to a new version and I've highlighted that they will have issues with certain spreadsheets / database applications ceasing to work correctly in the new regime. At last they've taken this on board and are looking to recruit a code monkey to fix the offending docs.

As I'm not a code monkey myself, I've no real idea of the skillsets they should be asking for in a JD. Anyone got any expeience of this or could point me at an existing JD out there for a similar role?

Long shot, but I thought I've give it a go. TIA

NN

Personally I would leave this one alone. Advise the client co of the need and let them go get the bod themselves. I am not quite sure what you are intending to do but reading the last line I guess you are going to bring a guy on and subcontract him or take a cut somehow? Bearing in mind you don't know anything about it do you think this is wise? It will come back on you if it goes wrong and bearing in mind you don't know what you are looking for this becomes a bit risky?

I presume your advice on docs working is based on testing and evidence rather than just a word of warning?

**bobspud** · 12 June 2012, 10:45

This can be a nightmare and needs a specialist team to manage. The normal conversation starts with a client saying "This should not be too hard to upgrade hell!! lets do it next week...." Only to find out a few weeks later that there were hundreds of Access 95 databases hidden all over the office that no one thought about...

There is compatibility with VB scripts, 32/64 bit versions and a million and then the bit where before you start the roll out, you need to install the compatibility packs so that those waiting to be upgraded can still _READ_ (although not always modify) documents created by new users...

**cojak** · 12 June 2012, 10:49

Originally posted by bobspud View Post

This can be a nightmare and needs a specialist team to manage. The normal conversation starts with a client saying "This should not be too hard to upgrade hell!! lets do it next week...." Only to find out a few weeks later that there were hundreds of Access 95 databases hidden all over the office that no one thought about...

There is compatibility with VB scripts, 32/64 bit versions and a million and then the bit where before you start the roll out, you need to install the compatibility packs so that those waiting to be upgraded can still _READ_ (although not always modify) documents created by new users...

Yep, I've done a Data/Config Management trawl on one of these converts - you'll be amazed at the amount of business criticality worms that crawl out of these things.

**garethevans1986** · 12 June 2012, 11:57

Which is why I hate Access.

GE

**escapeUK** · 12 June 2012, 12:00

Id make the case to clientco:-

Pros of upgrade: none

Cons of upgrade: everything stops working. Everyone has to relearn how to do stuff they have been doing for the last 15 years. (If you move from standard interface to ribbon)

Cost of upgrade £office x number of users + expensive contractor rate to try and fix all the things that would stop working

Lets face it Office 2000/XP does everything that 99% of users need to do. And there is none of the activate your license BS that plagues later versions.

**BrilloPad** · 12 June 2012, 12:01

Had a lovely one at previous job. Developers on office 2010. Users on office 2003. There are some spreadsheets created by 2010 that will not open with 2003 even if saved in 2003 format. Developers not allowed to migrate down. Users not allowed to migrate up. Chaos.

**BigTime** · 12 June 2012, 12:36

Originally posted by BrilloPad View Post

Had a lovely one at previous job. Developers on office 2010. Users on office 2003. There are some spreadsheets created by 2010 that will not open with 2003 even if saved in 2003 format. Developers not allowed to migrate down. Users not allowed to migrate up. Chaos.

I've a similar tale. I created a word doc that's 2003 compatible and insert an mpp which has also been saved as 2003 compatible. When the 2003 user tries to open the mpp it's no longer compatible so I had to send him the original file and have him insert it.

**NickNick** · 12 June 2012, 12:43

Originally posted by northernladuk View Post

Personally I would leave this one alone. Advise the client co of the need and let them go get the bod themselves. I am not quite sure what you are intending to do but reading the last line I guess you are going to bring a guy on and subcontract him or take a cut somehow? Bearing in mind you don't know anything about it do you think this is wise? It will come back on you if it goes wrong and bearing in mind you don't know what you are looking for this becomes a bit risky?

I presume your advice on docs working is based on testing and evidence rather than just a word of warning?

I'm not intending bringing anyone on site myself for this, as it's not my area, so I wouldn't have a scooby if they were any good at what they were doing. The reason for asking was that ClientCo has asked me if I've any ideas in this area as they don't, so I thought that I'd ask on here, in hopes of getting some initial pointers.

**NickNick** · 12 June 2012, 12:45

Originally posted by bobspud View Post

This can be a nightmare and needs a specialist team to manage. The normal conversation starts with a client saying "This should not be too hard to upgrade hell!! lets do it next week...." Only to find out a few weeks later that there were hundreds of Access 95 databases hidden all over the office that no one thought about...

There is compatibility with VB scripts, 32/64 bit versions and a million and then the bit where before you start the roll out, you need to install the compatibility packs so that those waiting to be upgraded can still _READ_ (although not always modify) documents created by new users...

That sounds about right, I've had a play with the OCCI and OPM from MS and it's easy enough to find what issues they will have, (which is in my remit) it's just finding the right person to fix them. (which is not, but I said i'd try and help)

Updating to Office 2010