converting back end to 2007m keeping front in 2003

[mjvm]

Hi,

My database (Access 2003) is split with the back end on the server and each person with a front end that is linked. Over time the computers/laptops are being replaced and almost everyone is on 2007.

I have read some of the earlier posts which advised holding off converting to 2007, but they were old and my first question is - should I be converting the database over?

If the answer to that is yes, can I convert the back end, and still have it accessed by 'old' front ends? I would like to have one person working with a converted front end, but not distribute it to everyone until it is working properly.

There is some VBA code in the front end, but I think the back end is fairly straight forward.

Thoughts/warnings?

Thanks for your help,

[mshmyob]

The back end only contains the tables and data and no code. The front end contains all the code.

You cannot convert just the backend to 2007 since it uses a completely different format that any other version.

You would need to convert a copy of the be/fe and let your single user fool with that to see if there are any problems before converting the main database.

cheers,

[mjvm]

Thank you.

If all the users are moving to 2007 and some changes are being made at the front end in 2007 (I know they won't work when open in 2003), should the database be converted? Can there be potential problems working across the two versions?

I have looked at Allen Browne's site for info on converting and also found on the microsoft site an Access 2003 Conversion tool that checks my database for any potential issues.

i am wondering whether to invest the time in converting something if it will continue to work the way it is.

[mshmyob]

If you just upgrade the FE to AC2007 that should be fine. I am not sure how the runtime if that is what you are using will work for a FE 2007 and a BE2003.

But if you are converting everyhting to an Office 2007 environment why not the entire database?

cheers,

@mjvm

[mjvm]

I was thinking that the back end would be easier to convert and so thought I could do that as my initial step. If I am converting the front end, the whole database will be done.

I provide the database service for someone else, and they need to know roughly what the conversion is going to cost them. I was wondering if someone would tell me not to bother - that 2003 works as well as 2007 - but that is not what I am hearing.

I guess if I run the conversion tool across it, that will tell me if there are potential problems, and then do a straight conversion - if it is all going to work, that shouldn't take long should it?

Sorry if this is really basic,

thanks for your advice,
marcella

[mjvm]

I wanted to add the following question - the current database does not use naming conventions. To rename everything will be time consuming - but probably straightforward in the back end, and then maybe rebuild the forms in the front end from scratch?

Its not a big database by your standards - there are a small number of forms and reports.

What do you think?