Access app running in 2000 -- moving to 2003 issues

[Goot]

Need some guidance. We have a consultant that created an access app that runs in Access 2000. Management wants his app to run in Access 2003, but the consultant is stating that due to profile issues and DLL's he can't move his application to 2003. Does this make sense?
What other issues could there be related to converting an app from 2000 to 2003.

Thanks much

 

[lupins46]

The reasons could be valid, but it's something a third party could only determine either by inspecting the database or by trying to convert it.
I assume you are expecting to pay your consultant for this, if he does it. If so, then I would suspect he is right and the application requires more than just a straightforward conversion to run in A2003.

Have you tried to run it in A2003?

 

[alvechurchdata]

The reasons could be valid, but it's something a third party could only determine either by inspecting the database or by trying to convert it.

I'd agree. Access stays much the same on the surface between versions but underneath the covers there are all sorts of uncertainties.

Geoff Franklin

http://www.alvechurchdata.co.uk

 

[PCLewis]

I tend to think the opposite. You would have to have some pretty weird stuff in an Access 2000 database that would prevent it working in 2003. I am assuming the operating system of the machine running the application is the same in both cases.

If you have the mdb then it's easy for you to just try it.

But regardless of whether it works or not, you might be better off getting the consultant in if you want to keep him supporting you

 

[lupins46]

'You would have to have some pretty weird stuff in an Access 2000 database that would prevent it working in 2003.'

So I take it that you can see from where you are sitting that there is none in the application in question?
No, of course not.

It is perfectly possible that the consultant is just trying to bamboozle the user with some techie words and there is no reason why the app would not convert.

But there are hundreds, if not thousands, of MS and 3rd party addins available and the use of any one of them in an Access app might inhibit conversion. So the consultant' comments could be valid. Unless you look at the app and/or try to convert it, you can't reach any conclusion.
And A2003 imposes more constraints on what is acceptable design in security terms so things which did work in earlier versions do not work any more.
I am thinking particularly of the use of several of the built-in functions in object properties (which appears to be a more widespread practice than I ever realised, as i don't do it at all!). These have now been re-classified as dangerous and cannot be used in object properties which means the app requires (usually small) changes to the design and code.

If I were the consultant and said the app will not convert simply and the user tried the app in A2003 and it ran perfectly, then I would not expect a profitable ongoing relatonship from then on would you.