Question Copying a DB after split

[johntology]

Hello,

I have users working with a DB that I've split. I now need to make some changes to the DB on a development copy. (Need to add some fields and tables, write some VB, and more.) What is proper way to do this? If I just try to resplit the front end to point to a new backend, Access tells me that the backend table is empty. However, when I open the DB it appears that everything is there. So I'm not sure what's going on in the background. I suspect that there's a pointer back to the production version, which would be a bad thing. I need the development version to be completely independent of the production version.

Should I copy both the front- and backend files then point the new front to the new back? How do I do this? (Couldn't find where to re-point.) Or is there a way to unsplit and resplit?

Thanks.

 

[boblarson]

You only split the database ONCE. You put the backend up on the server location and then each user gets a copy of the frontend. You maintain a master copy of that frontend and you would do your changes there and then just give everyone a new copy. However, if you have changes that need to be made in the backend, then you would do that first (but everyone needs to be out of the database - all frontends closed) and then you would do your frontend design changes (including linking up the new tables from the backend) and then redeploy a copy of the front end. There is no splitting again.

 

[johntology]

You only split the database ONCE. You put the backend up on the server location and then each user gets a copy of the frontend. You maintain a master copy of that frontend and you would do your changes there and then just give everyone a new copy. However, if you have changes that need to be made in the backend, then you would do that first (but everyone needs to be out of the database - all frontends closed) and then you would do your frontend design changes (including linking up the new tables from the backend) and then redeploy a copy of the front end. There is no splitting again.

Thanks, Bob. But suppose I need to spend several days in development, during which my users need to keep working. Wouldn't I need a parallel, independent copy of both the front and back ends? If so, how do I copy the pair and retain a link between front and back? My plan is to take my time doing development and record all my work in a log. When finished, I would lock users out of the production version and execute all of the same changes there. Is this the kind of work flow that most people do? Or is there a better way?

John

 

[boblarson]

1. The backend you can do the changes in a copy of the backend and then do the changes to production like you have said.

2. For the frontend, it SHOULD be a matter of just using your master copy and making the changs (and having it linked to your copy of the backend so you can use the new tables and fields) and then you just relink to production after the backend changes are done. And then just redeploy to your users.

3. If the database is properly normalized then you normally would not have backend changes to make as adding tables and/or fields is a very RARE event.

 

[johntology]

1. The backend you can do the changes in a copy of the backend and then do the changes to production like you have said.

2. For the frontend, it SHOULD be a matter of just using your master copy and making the changs (and having it linked to your copy of the backend so you can use the new tables and fields) and then you just relink to production after the backend changes are done. And then just redeploy to your users.

3. If the database is properly normalized then you normally would not have backend changes to make as adding tables and/or fields is a very RARE event.

Thanks again. Your second comment brings me back to my starting point. How do I establish this link between development front end and development back end when I'm using copies of an already-split DB? I don't see such an option in Access. I see Split, but I don't see anything like "re-point."

 

[boblarson]

To link the frontend to the development backend you would use the Linked Table Manager. While in the frontend, you get to that by

In Access 2003 and earlier:

Go to Tools > Database Utilities > Linked Table Manager

in Access 2007 and higher

Go to the DATABASE TOOLS tab in the Ribbon and then over to the right you should see Linked Table Manager.

Once you bring that up, you select all of the tables to relink and then check the ALWAYS ASK checkbox down at the bottom left. Then click OK and it will bring up a dialog where you can go select the development backend.