Prev: Form with combo box to set criteria for query and report
Next: Inventory/Sales/Warehouses
From: MJ on 30 Apr 2010 12:31
I am sure that someone has asked this at one time or another, but haven't
found it out here yet.

I have several inter-related databases, some of them have linked tables
while others have queries appending to tables which they are not linked to.

What is a good rule of thumb for when it makes better sense to link to a
table rather than simply appending to a table? What are the PROs and CONs?

Thank you in advance for your informed inputs.

--

MJ
From: Steve on 30 Apr 2010 13:46
Linking to a table refers to having a backend database of tables only and
linking to the tables from the frontend on each user's computer. All
databases ought to be split excpt where you can say with 0ne-hundred percent
certainty that the database will always be a single user database. Linking
to tables and appending to tables are two separate distinct issues and one
can not be substitued for the other.

Steve
santus(a)penn.com


"MJ" <MJ(a)discussions.microsoft.com> wrote in message
news:8D2D8C6C-FA84-4D4B-B944-19C2D13573EE(a)microsoft.com...
>I am sure that someone has asked this at one time or another, but haven't
> found it out here yet.
>
> I have several inter-related databases, some of them have linked tables
> while others have queries appending to tables which they are not linked
> to.
>
> What is a good rule of thumb for when it makes better sense to link to a
> table rather than simply appending to a table? What are the PROs and
> CONs?
>
> Thank you in advance for your informed inputs.
>
> --
>
> MJ


From: Fred on 30 Apr 2010 14:01
Linking and appending are for completely different purposes, and so there is
no basis for a general "either/or" type question.

Perhaps if you could give the specifics of something that you want to do, we
could tell you which to use for that purpose.


From: MJ on 30 Apr 2010 14:52
Ok gentlemen, perhaps I did not word my question correctly.

1) [Steve] I understand FE/BE splitting, so need to beat it into ground.
Also, understand difference from a linked table vs appending to a table.
2) [Fred] The question was general in nature... wahat are the pros & cons

Specifics: I have DB1 that serves as the source for info to be appended to
a table in DB2. It currently does this using the URL of DB2, vice linking
the table in DB2. It works.

What I am looking for other experienced Access users, are there any
advantages or disadvantages to linking the table from DB2 to DB1 and simply
appending the info to the now "local" table (linked)?

* I see them as 2 ways of doing the same thing, wondering if one is
better than
* the other, or if the are real tradeoffs that should be considered in
doing it one
* way over the other.

I hope this clarifies my questions. Once again, thank you for your response
and taking time out to help another.

--

MJ


"MJ" wrote:

> I am sure that someone has asked this at one time or another, but haven't
> found it out here yet.
>
> I have several inter-related databases, some of them have linked tables
> while others have queries appending to tables which they are not linked to.
>
> What is a good rule of thumb for when it makes better sense to link to a
> table rather than simply appending to a table? What are the PROs and CONs?
>
> Thank you in advance for your informed inputs.
>
> --
>
> MJ
From: John W. Vinson on 30 Apr 2010 16:00
On Fri, 30 Apr 2010 09:31:01 -0700, MJ <MJ(a)discussions.microsoft.com> wrote:

>I am sure that someone has asked this at one time or another, but haven't
>found it out here yet.
>
>I have several inter-related databases, some of them have linked tables
>while others have queries appending to tables which they are not linked to.
>
>What is a good rule of thumb for when it makes better sense to link to a
>table rather than simply appending to a table? What are the PROs and CONs?
>
>Thank you in advance for your informed inputs.

If by appending you mean that you're copying data from one database into new
records in a table in another database, just be aware that you now have *the
same* data stored in two different places. This is called Redundancy, and it's
generally considered a bad thing to do!

Suppose you append some data from BigJoe.mdb into Mylocal.mdb. The guy in
charge of BigJoe realizes that some of this data is incorrect, and goes in and
corrects the errors.

You now have two copies of the data. They're different. One of them is wrong
(yours, as it happens, but how can you tell?).

Not only are you wasting space but you now have wrong data in your database,
and no way to reliably detect that it is wrong.

The only time I'd use an append is when you intentionally want a point-in-time
snapshot of the current data in BigJoe, realizing that it may be out of date
at any later time.
--

John W. Vinson [MVP]
 |  Next  |  Last
Pages: 1 2
Prev: Form with combo box to set criteria for query and report
Next: Inventory/Sales/Warehouses