Question Exporting from Access 2007

[addACUMEN]

Apologies for a really silly question but I am stumped.

I have limited experience of sharing Access databases but I have never met any problems before. I am now attempting to work with a fellow Committee member to sort out our Membership database. She is a senior Civil Servant with a work laptop and a personal laptop. I am a retired IT professional (though not a Windows person) with a modern laptop.

She sent me a back up copy of the database which appeared to be in Access 2002 (name.mdb). I opened it in my copy of Access 2007 and explored it. I have sent back small database objects to prove that we have two way sharing but nothing I send can be opened by her.

I have tried all the options available in Access 2007, that is Access 2002-3 and Access 2000 - I am now wondering about writing SQL text files for her to try.

There must be an easier way. Can you put me out of my misery?

Thanks for your help

 

[HiTechCoach]

Welcome to AWF!

Is the database split (Front end and Back end)? My guess would be probably not. I would urge you to do this. It sure makes life a lot easier with remote development.

See:
Splitting a access database, or how to run ms-access in a multi-user mode.

 

[addACUMEN]

The database is a mess. I am planning to remodel it so that it is less of a mess.

What I mean is that there is considerable duplication of data and while there are some foreign key relationships they are not managed by the database. The Membership Secretary keeps them in step manually. And, given that, I guess you would expect it not to be a split database. It isn't.

What I had planned as the development path was to exchange progressively more functional databases with her. And that plan requires that I am able to send her databases which she can open.

And, for the moment, that is my major problem. Any suggestions?

 

[HiTechCoach]

The database is a mess. I am planning to remodel it so that it is less of a mess.

What I mean is that there is considerable duplication of data and while there are some foreign key relationships they are not managed by the database. The Membership Secretary keeps them in step manually. And, given that, I guess you would expect it not to be a split database. It isn't.

What I had planned as the development path was to exchange progressively more functional databases with her. And that plan requires that I am able to send her databases which she can open.

And, for the moment, that is my major problem. Any suggestions?

That is exactly why I suggested you need to split the database into application (Front end) and data (back end). If you do that, then you will have what you need to easily send updates out.

You do not need to make any design changes to split the database. By splitting the database, it makes cleaning it up a whole lot easier. You can even have two version using the same data!

 

[datAdrenaline]

- When you opened the file in A2007 did you convert it? to A2007?
- "I have sent back small database objects" ... what do you mean by this... Do you crate a stripped down version of the db? ..
- If you create files for her, I would suggest that you set the default file format to mdb (Office Button > Access Options > Popular > Default File Format, then choose the appropriate one). Due take note that this effects the Office Button > New, but changing this setting does NOT effect the Right Click on Desktop > "New" > "Microsoft Access 2007 Database" desktop shortcut method for create

In addition to all this, you need to make sure your VBA references the right libraries! For example, you should ensure you are pointing to the same DAO library (Microsoft DAO 3.6 Object Library) since your partner will NOT have the A2007 DAO library (Microsoft Office 12.0 Access Database Engine Library) available to her.

Aside from that ... spliting is THE way to handle multiple developers, just as Boyd has advised.