I have one Design Master and one Replica linked to tables in a back-end database. Because this is a 'work-in-progress' database as well as a usable one, I have fairly frequent changes to my Front-end that need to be reflected in the replica.
My problem is that each time I synchronize with the replica from the design master so that it is up to date with the latest changes, the links to the tables are replicated too and I have to go to the replica and use the Linked Table Manager to re-establish the links to the b-e.
This isn't too much of a problem at the moment (except it annoys my colleague when I have to kick her off her machine) but obviously this is going to be impractical if the number of users starts to climb. I don't want to have to go around half-a-dozen machines for example and have to update the links on them all.
Any suggestions?
Thanks in advance.
Quote for the day: "If you don't tell you're partner how much you care the rest of the year, what's the point of Valentines day?" (Soppy I know but it is the season
My problem is that each time I synchronize with the replica from the design master so that it is up to date with the latest changes, the links to the tables are replicated too and I have to go to the replica and use the Linked Table Manager to re-establish the links to the b-e.
This isn't too much of a problem at the moment (except it annoys my colleague when I have to kick her off her machine) but obviously this is going to be impractical if the number of users starts to climb. I don't want to have to go around half-a-dozen machines for example and have to update the links on them all.
Any suggestions?
Thanks in advance.
Quote for the day: "If you don't tell you're partner how much you care the rest of the year, what's the point of Valentines day?" (Soppy I know but it is the season