Re: Replication for Access

I imported the tables, forms, queries, reports, and modules into and new
database and regenerated the tables and links to create a new unreplicated
database. Then I split the database as suggested.

When I try to replicate the data file it keeps saying the file is all ready
in exclusive use and then stops. If I am doing this wrong please explain the
right way.

"David W. Fenton" wrote:

> =?Utf-8?B?RnJhbmsgTWFuc2ZpZWxk?=
> <FrankMansfield@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
> news:A24479E6-793A-42DF-BBBE-007FF4892E6B@xxxxxxxxxxxxx:
>
> > I have replicated a 2003 Access database, but I have included
> > forms, queries and tables. If the forms and queries are not
> > replicated how will the replicated database have access to the
> > forms and queries?
>
> You send them a separate, non-replicated MDB file with the
> forms/reports/queries.
>
> How do you push out changes to those?
>
> You send out a new one.
>
> See http://www.granite.ab.ca/access/splitapp/index.htm for an
> explanation of all the considerations in splitting an application.
>
> It's standard practice to split -- I do it even for apps used by a
> single user. The original justification was for multi-user apps,
> where you put the data MDB on the server, and a copy of the front
> end on each workstation.
>
> If you're unsplit (absent a mechanism like replication, or a lot of
> code that copies in new objects) how do you make changes to the
> front end without overwriting the user's data?
>
> Replicating front ends looks like a great idea, a solution for this,
> but if you understand the way replication works (and especially the
> changes to the way the Access project is stored that came with A2K),
> you realize that it's a *very bad* idea -- it amounts to splitting
> your app and having multiple people open the front end at the same
> time (which is also a bad idea of another kind).
>
> From a design point of view, forms and reports are read-only for
> everybody but the developer of the application. From a user's point
> of view, the form/report definitations are read-only. But in
> reality, behind the scenes, some properties are actually saved in
> the background (such as filters/sorts), and those end up getting
> exchanged during synchs of replicated forms/reports. The result is
> dueling form properties, and a lot of unnecessary synchronization of
> information that has no value anywhere except for the individual
> user.
>
> The bottom line: don't replicate what is not shared.
>
> And forms/reports are not shared in the sense that the data tables
> are.
>
> --
> David W. Fenton http://www.bway.net/~dfenton
> dfenton at bway dot net http://www.bway.net/~dfassoc
>
.

Relevant Pages

  • Re: running report cause fatal error- on Win98, not XP
    ... It is actually not that difficult to crash JET with complex queries, ... another query. ... only the more complex reports cause the crash- the others do ... Then compact the database: ...
    (microsoft.public.access.reports)
  • Re: Any tips on working with a database that you did not create?
    ... am new to Access and taking over an entire database. ... In fact it had been thrown together using wizards ... Look through the queries and spot whether any of them are anything other ... Look at the reports. ...
    (microsoft.public.access.gettingstarted)
  • Re: Any tips on working with a database that you did not create?
    ... am new to Access and taking over an entire database. ... In fact it had been thrown together using wizards ... Look through the queries and spot whether any of them are anything other ... Look at the reports. ...
    (microsoft.public.access.gettingstarted)
  • Re: Any tips on working with a database that you did not create?
    ... I was given what looked like a "nearly finished" database which apparently represented a great deal of work. ... In fact it had been thrown together using wizards based on a wholly wrong table structure. ... Check to see if the database has "linked tables" - a common way of building a database is to put the tables in one file and all the queries, forms and reports in another, and link the two. ...
    (microsoft.public.access.gettingstarted)
  • Re: Designing a new DB
    ... Stay with one table and use queries and/or reports to group your data by ... ACC2002: Database Normalization Basics ... Database Normalization Tips by Luke Chung ... > There will be simple calculations in certain fields in both the> monthly and annual reports. ...
    (microsoft.public.access.gettingstarted)