Database changes on FE/BE

Hi,

I have a shared database between 6 users using the FE/be design on Acess
2000.The switchboard works fine for all except for when i need to make a
change like add a different button on the master copy and copy this front end
to another users desk.This one change affects all the other users with an
error since their front end does not have this one change.Can i not custom
make a design independant of what the other users?
Thanks

I am not clear from your description what is happening.

If each user's PC has its own copy of a front-end, each copy is independent
of the others.

Any changes you make to YOUR copy should have no affect on anyone else's
copy.

But your description mentions that you are trying to "copy this [?new
master?] front end to another users desk". If a new version of the front
end is working on your PC and is copied to one other PC, how does "this one
change affect[s] all the other users"?

--
More info, please ...

Jeff Boyce
Access MVP

"jk" wrote in message
...
Hi,

I have a shared database between 6 users using the FE/be design on Acess
2000.The switchboard works fine for all except for when i need to make a
change like add a different button on the master copy and copy this front
end
to another users desk.This one change affects all the other users with an
error since their front end does not have this one change.Can i not custom
make a design independant of what the other users?
Thanks

Hi,

I have one master DB..it is a front end/back end design with a shared folder
on the network. I copied and pasted this master DB to my desktop so i could
work on it from my desktop to make a change.I made one change to one button
of the switchboard on this copy on my desktop.I closed and saved the
change.....i went back to the orginal master DB and the change i made to the
copy transferred to the master DB.This one change affected the users the
users as well and they had errors when they opened their db.When i reversed
the change on the copy back the way it was,,,,,,,no more errors
occurred.Please advise

"Jeff Boyce" wrote:

I am not clear from your description what is happening.

If each user's PC has its own copy of a front-end, each copy is independent
of the others.

Any changes you make to YOUR copy should have no affect on anyone else's
copy.

But your description mentions that you are trying to "copy this [?new
master?] front end to another users desk". If a new version of the front
end is working on your PC and is copied to one other PC, how does "this one
change affect[s] all the other users"?

--
More info, please ...

Jeff Boyce
Access MVP

"jk" wrote in message
...
Hi,

I have a shared database between 6 users using the FE/be design on Acess
2000.The switchboard works fine for all except for when i need to make a
change like add a different button on the master copy and copy this front
end
to another users desk.This one change affects all the other users with an
error since their front end does not have this one change.Can i not custom
make a design independant of what the other users?
Thanks

"jk" wrote in message
...
Hi,

I have one master DB..it is a front end/back end design with a shared folder
on the network. I copied and pasted this master DB to my desktop so i could
work on it from my desktop to make a change.I made one change to one button
of the switchboard on this copy on my desktop.I closed and saved the
change.....i went back to the orginal master DB and the change i made to the
copy transferred to the master DB.This one change affected the users the
users as well and they had errors when they opened their db.When i reversed
the change on the copy back the way it was,,,,,,,no more errors
occurred.Please advise

Either you somehow have replication going on here or you actually made a
shortcut to your desktop and not a copy.


--
I don't check the Email account attached
to this message. Send instead to...
RBrandt at Hunter dot com

Thanks Rick,

Could you advise on this .......When you have the front end on your desk top
and there is a user that needs a design change on the existing front end.How
do you go about it?I just dont understand how making a copy of the existing
mdb on my desktop just to make a design change for one of the users would
transfer that change over to the master.All i did was right click the master,
click copy and paste to the desktop ...what am i doing wrong?

"Rick Brandt" wrote:

"jk" wrote in message
...
Hi,

I have one master DB..it is a front end/back end design with a shared folder
on the network. I copied and pasted this master DB to my desktop so i could
work on it from my desktop to make a change.I made one change to one button
of the switchboard on this copy on my desktop.I closed and saved the
change.....i went back to the orginal master DB and the change i made to the
copy transferred to the master DB.This one change affected the users the
users as well and they had errors when they opened their db.When i reversed
the change on the copy back the way it was,,,,,,,no more errors
occurred.Please advise

Either you somehow have replication going on here or you actually made a
shortcut to your desktop and not a copy.


--
I don't check the Email account attached
to this message. Send instead to...
RBrandt at Hunter dot com

"jk" wrote in message
...
Thanks Rick,

Could you advise on this .......When you have the front end on your desk top
and there is a user that needs a design change on the existing front end.How
do you go about it?I just dont understand how making a copy of the existing
mdb on my desktop just to make a design change for one of the users would
transfer that change over to the master.All i did was right click the master,
click copy and paste to the desktop ...what am i doing wrong?


Actually there is a third possibility. In another post you said this form was a
Switchboard. The buttons shown and actions provided by a switchboard are drawn
from a table. If that table is on a shared back end then a change on one front
end _will_ show up on the others.

This hadn't occurred to me earlier as I never use the Switchboard provided by
Access.


--
I don't check the Email account attached
to this message. Send instead to...
RBrandt at Hunter dot com