converting from access 2003 to future versions

[rob1234]

I've been hired to clean up and convert a flat filemaker database into access 2003 and I've spent the last two weeks learning the ins and outs of access and doing preparations. Well, today some high up database guy in another department told me not to use access because in the future when a new version of access comes out we will have to recreate the database from scratch because there are lots of problems converting between versions. I'm aware there might be some hiccups but I don't really agree with him. Plus once the database is up and functioning I don't see why we'd even have to upgrade it to a new version. It's just a small health centre patient database with info about patients and their treatments. Does anyone have any opinions about this. Thanks.

 

[RV]

Does anyone have any opinions about this

You're right.
New versions will come with new versions but that doesn't mean that you'd have to rebuild from scratch.
Since the day Access was born, there have been quite a couple of new versions and I've never ever met somebody that stated "bugger, now I'll have to rebuild my applic from scratch".

Tell the database guy to stick to what he really know, stay far 'way from Access and not to spread what sounds to me like sheer nonsense

RV

 

[ghudson]

Upgrading has never been a problem for me and my applications. Access 2 to Access97, Access 97 to Access 2003. Sure there were a few custom functions that had to be adjusted with some minor VBA changes but nothing to loose any sleep over.

 

[rob1234]

That's what I thought. I just got off the phone with him. Apparently, he hasn't really worked with Access before. He just knows people that have had problems with programs they have written that interact with Access db's when converting between versions. He meant that the programs would have to be redone not the database. But I don't think this will be a problem as I'm fairly sure we'll be using an Access front end anyway.