How to use access 2003 db with access 2010?

[Unicon]

Dear all,

I have a database in access 2003, now we move to office 2010. Can I still use that 2003 database in access 2010?? If yes than how to use?? or I have to forget about my 2003 database?
Please advice.

 

[CBrighton]

I expect Access 2010 will have a tool for changing the format to a new accdb file (2007 does, not used 2010).

I'd advise backing the database up first though.

 

[Galaxiom]

I expect Access 2010 will have a tool for changing the format to a new accdb file (2007 does, not used 2010).

I have not used 2010 but 2007 happily runs mdb database. I expect this will be the case for 2010 also.

Very few worthwhile reasons to bother changing to the later format and several good reasons why not. If the database is working fine then let sleeping dogs lie.

When it comes to upgrading to 2007 accdb, absolutely forget it. There are zero worthwhile reasons to upgrade and very, very good reasons to not do it.

 

[the_net_2.0]

I have not used 2010 but 2007 happily runs mdb database. I expect this will be the case for 2010 also.

the only major difference in 2010, aside from all the new functions, is the data macro bs. And that should never be used, as it's a pointless addition to the program.

2010 does still run mdb files. But if by some miracle they don't, I'm sure Bob Larson will correct me. Wow, shouldn't have said that, but I like teasing him.

The macro structure is also different, which may very well be part of the causality of backward compatibility being a problem.

 

[CBrighton]

What about if some users are using 2003 with it's native mdb format and some are using 2007 accessing mdb's in backwards compatibility?

I find the references in the mdb get messed up as the folder which they are stored in differs between the versions of Office.

 

[the_net_2.0]

What about if some users are using 2003 with it's native mdb format and some are using 2007 accessing mdb's in backwards compatibility?

I find the references in the mdb get messed up as the folder which they are stored in differs between the versions of Office.

yes, the refs get messed up. I would assume the only way to counter this possibility is to ensure that your refs being used are only those that are common to all OS versions and/or access versions.

 

[CBrighton]

I just have 2 front ends, one mdb and one accdb.

 

[Galaxiom]

I find the references in the mdb get messed up

Late binding solves most of that.

 

[boblarson]

the only major difference in 2010, aside from all the new functions, is the data macro bs. And that should never be used, as it's a pointless addition to the program.

2010 does still run mdb files. But if by some miracle they don't, I'm sure Bob Larson will correct me. Wow, shouldn't have said that, but I like teasing him.

The macro structure is also different, which may very well be part of the causality of backward compatibility being a problem.

Yes, I will correct you. Data macros are actually integral in the ability to use the Access Web Services of SharePoint 2010. You do not have the ability to use VBA in Access Web Services, so you have to do some things within the data that you would normally not do in other situations. Now, data macros can also be likened to SQL Server Triggers which are also useful and not pointless. So data macros are QUITE ALRIGHT TO BE USED and are indeed USEFUL.

Access 2003 files can be run by Access 2010 but you should not mix the two. Everyone should have 2010 or 2003 but not some one one and some on the other or else you will possibly end up with problems. However, Access 2003 files (or previous versions - using mdb files) will not have data macros available (only available to 2010 and if you use any in 2010 then your file will not run in Access 2007).

The new macro structure is quite good and is a good bridge between macros and VBA. They are more powerful than ever and include error handling and looping, which previous macros can't do. But again, most of that is not available with mdb files as they have a different macro structure and do not know about the newer stuff.

 

[gemma-the-husky]

i think a lot more problems occur when you try and use mdes/accdes

because you cannot change references in an mde/accde - you can get problems moving a standard database from one platform to another, depending on the level of dlls used -

so design at the lowest level, so that problems can resolve themselves. if you design in A2003 with outlook 11 library, then this should work fine on an accde. however, if you build a A2007 accde/mde on a machine with office2007, and then try to run it on a machine with say office2003, but access 2007 - you have a problem. your app cannot find the outlook12 library, and you have no way of telling it to use the outlook 11 one.

As Galaxiom says, and I am finding out, changing your code to use late binding makes it easier for your apps to be less pernickety about the actual runtime environment, if you will.