You have outlined the very reason why you should split your database into
frontend (all objects except tables/relationships) and backend (just the
tables/relationships). The frontend contains links to the tables in the
backend.
You would put the backend on a server and give each user a copy of the
frontend on their computer.
Once you have completed any changes on your copy of the frontend, you would
distribute it to users, over-writing their copy of the frontend; data
wouldn't be affected at all. You can automate the updating of frontends
using a utility like
http://www.granite.ab.ca/access/autofe.htm

Signature
Joan Wild
Microsoft Access MVP
> Firstly can somebody please tell me if it is possible to do a database
> design
[quoted text clipped - 4 lines]
> and
> then bring it back on after a design change?
Doreen - 16 Aug 2005 16:27 GMT
Yeah my database is split into two and there are a few fields that I would
want to add to my front end as well as validation rules and stuff like that.
Will this not affect my tables?
> You have outlined the very reason why you should split your database into
> frontend (all objects except tables/relationships) and backend (just the
[quoted text clipped - 18 lines]
> > and
> > then bring it back on after a design change?
Joan Wild - 16 Aug 2005 16:33 GMT
> Yeah my database is split into two and there are a few fields that I would
> want to add to my front end as well as validation rules and stuff like
> that.
> Will this not affect my tables?
Fields are in the backend tables (not usually in the frontend). Validation
rules may be in the tables or they may be on a form.
If you are making any design changes to the backend, then you will need to
do this when no one else is using it. I believe you said in your other
message that you want to send it to someone else to make the changes. In
that case, you'll need to send them the backend. While it is in their
hands, you won't be able to make any data changes in your copy of the
database. When they send it back you'll overwrite your backend with the
newly updated one.

Signature
Joan Wild
Microsoft Access MVP
There is no automatic way to do this. You could modify a copy, then use
queries or copy.paste to move the data into the new structure, but depending
on your changes this may not always work smoothly. Why would you not just
change the actual file (after saving a backup)?

Signature
Rick B
> Firstly can somebody please tell me if it is possible to do a database design
> change on a separate copy of my database and then bring it on to update the
> one I am using. Does this have any effects on my data already in the
> database? Secondly is it possible to seperate my data frame from the data and
> then bring it back on after a design change?
Rick B - 16 Aug 2005 16:11 GMT
Joan has a good point. For some reasoon I read your question to mean that
you were trying to change the tables, not the other objects.

Signature
Rick B
> There is no automatic way to do this. You could modify a copy, then use
> queries or copy.paste to move the data into the new structure, but depending
[quoted text clipped - 9 lines]
> and
> > then bring it back on after a design change?
Doreen - 16 Aug 2005 16:21 GMT
Thing is I'm not the one who designed this database in the first place,
though i have the permissions to change it. So the person who designed it is
somewhere else and there are changes i wanted. I was hoping they can update
the copy they have and send it to me.
> There is no automatic way to do this. You could modify a copy, then use
> queries or copy.paste to move the data into the new structure, but depending
[quoted text clipped - 9 lines]
> and
> > then bring it back on after a design change?
Rick B - 16 Aug 2005 16:29 GMT
That would depend on what they are changing. If they are simply changing a
form/report/query, then they can do that and then you can drag that new
object into your copy.
If they need to change the tables, then that complicates it a bit.
Have you tried asking the person who built it? I would think they would be
the one posting here if they have questions.

Signature
Rick B
> Thing is I'm not the one who designed this database in the first place,
> though i have the permissions to change it. So the person who designed it is
[quoted text clipped - 14 lines]
> > and
> > > then bring it back on after a design change?