Hey guys,

I have a Database that's running live in the Office, but in my own time at home I'm working on development and adding additional features. I've added some features into the database by adding extra pages to the Tab Control and adding SubForms/Macros to that page, all contained within the "Home" Form - I've tested them all and I'm happy to unleash them on the office now!

What's the best way to implement the change? My copy that i've been working on is now a couple of days old (data-wise) whereas the version live in the office has an extra 3 or 4 day's-worth of records. Can I just safely delete the Home Form in the office version and import mine, or is there an automated way I can import all the records that the office version has but my version doesn't?

Your database should be split... the data should remain in the back end and the front end should have everything else with linked tables to the back end.

Check this wiki article : http://www.UtterAccess.com/wiki/index.php/Sharing

It's always good practice to "Split" the database into a "Backend" (containing nothing but the tables) and a "Frontend" (containing links to the tables, along with all the queries, forms, reports and code). This is essential for a multiuser system!

You can use the "Database Splitter Wizard" to split the database; the backend (Access will add a _BE to the database name) should go into a shared folder accessible to all users, and each user should get their own private copy of the frontend. You will then be able to make any design changes you need to the forms, reports, etc. in your master copy of the frontend (linking to a "test data" backend, so you can test the forms without hurting the production data), and then use the Linked Table Manager to relink to the production backend. The users' copies of the old frontend can simply be discarded and replaced with the new frontend.

Hi,

Thanks for that - I've followed the information in the link and split by database into a FE and a BE.

Everything has worked fine, with the exception of one thing. My "Add New Order" button on my Home form no longer works. I get the error "The record source 'Order' specified on this form or report does not exist". I've checked the record source in the properties of the Form and the Orders table is available to choose in the dropdown, so i'm not sure why it won't work. I've got a different button that add a new customer, and that works fine, which just confuses me even more!

Edit - just to add, if I link the tables using my master copy on my local machine, create the ACCDE and e-mail to the other users, the "Add New Order" button fails as above. However if I email out the ACCDB file and then create the ACCDE file locally on each machine it works fine (IMG:style_emoticons/default/iconfused.gif)

This post has been edited by sliz: May 29 2012, 03:14 AM

Please post the VBA code (or macro, if that's what you used) executed by the Add New Order button. We can't see it from here! (IMG:style_emoticons/default/iconfused.gif)