Bill:
I think I understand but want some clarification. One file with just the tables and one file with the forms, reports, queries, etc, correct?
If that is correct, how time consuming is it going to be to change the source locations for the forms, etc. Also, is there a way to specify relative locations in the data source as these will be on a network file server at two (possibly more) sites.
Thanks again and sorry if these are really N00Bish questions....LOL
Rob
--- In MS_Access_Professionals@yahoogroups.com, "Bill Mosca" <wrmosca@...> wrote:
>
> Rob
>
> Replication is pretty much dead these days. And what you are talking about really isn't replication since data syncing is not the issue; it's design changes.
>
> If you split the databases into a back end with the tables and a front end with everything else, you can make design changes to forms, reports, etc. without affecting the data.
>
> Then you just over-write thet existing front end with your new one.
>
> Regards,
> Bill Mosca, Founder - MS_Access_Professionals
> http://www.thatlldoit.com
> Microsoft Office Access MVP
> https://mvp.support.microsoft.com/profile/Bill.Mosca
>
>
>
> --- In MS_Access_Professionals@yahoogroups.com, "rpmazur0169" <rpmazur@> wrote:
> >
> > OK. I started a database (put a lot of work into it too) in accdb format. Now I want to replicate this database in two different places with the master on my workstation.
> >
> > Any way to do this since I know that I would have had to keep oit in the MDB format from days gone past. Or, conversely, if I have to make changes to the database, can I push those design changes to my "replicas" without effecting the data?
> >
> > I need to use the database at two different sites (with different sets of data contained within the tables). I'll be honest, I didn't think this database would be used in two different places when I designed it. LOL
> >
> > Thanks in advance.
> >
> > V/R
> >
> > Rob
> >
>
Tidak ada komentar:
Posting Komentar