Split Database Design Change

[rhonda6373]

Good morning,

I have a client that has sent me a database that is already split. I have not worked with a split database before.

He wants me to make the changes and then re-import data from the database they are currently using so that the data will be current.

He asked if you have to re-split the database after making changes, is that true?

I cannot find anything that says you have to re-split. I was going to make design changes to the front end, table changes to the back end, then import the current data into the back end. Is my approach correct?

Can anyone answer those two questions?

Thanks!

[Seth Schrock]

If the database is truly split, then the tables in the front-end are only linked. If you are only making changes to the front-end, then you don't have to do anything with the backend. If you have to add/remove fields in the backend, then all you have to do is refresh your tables in the front-end.

However, since you say that he wanted you to re-import the data, that makes me wonder if it is truly split or if you have some sort of manual transferring of records between two databases.

[twinnyfo]

Also, with a split database, the DBA can have a "false" back end, so that you can test the functioning of your forms and reports without destroying the "real" data. Just make a copy of the back end and link the FE to that copy. Then, when you are ready to go live, link the FE back to the old Back end - of course, as Seth mentions, any changes to BE tables must be accounted for.

[rhonda6373]

Thanks for the suggestions! I will do that.

[twinnyfo]

Let us know if you run across any hitches. We'll be glad to assist if we can.

[rahulsankhe1089]

i think this is the correct approach
i would have done the same