Old Access App - What should I do?

[silas2]

I developed a system in Access 2k 10 years ago. At the time I was a full-time Access developer and the project was (thankfully!) done with clean VBA throughout and, as per usual with Access has been 100% reliable.


I just got a call from the original sponsors of the project who want to push the app out to many more sites, (its an enormous UK public body), amazingly there hasn't been anything else created in the mean time with the same functionality.
My question is, being a bit out of touch with Access now and remembering the blood and sweat spilled over the Office 2k Developer Tools and install issues with the runtime executeable,and the problems with different versions of Access side by side, etc.. what is the best way to go if this comes off?
My only issue is with install + side by side with other Access versions + remote support, what do other people do now?

[ajetrumpet]

what do other people do now?

what do you mean "what do other ppl do now?"

the concept of deployment is pretty much the same, if that's what you mean.

[silas2]

I did see some 3rd party installers advertised for Access, does anyone have any experience of them?

[silas2]

I've just been looking at some more stuff, and I realise that Access 2007+ no longer supports User Level Security, plus I think there are issues with the menus becoming ribbons, so I'm stuck with 2000, 2002 or 2003.
I know there's isn't one difinitive answer to deployment, but is there a reason why staying with 2000 (over going to 2003) might cause problems?