Let us say that one runs a make table query on
some data one day.

And some days later the same query is run on the
data, but some records have been added and
subtracted.

Is there a good method using access to compare
the two tables?

I think it's impossible, sorry.

"tom" <(E-Mail Removed)> wrote in message
news:qZ_8h.375$(E-Mail Removed)...
> Let us say that one runs a make table query on
> some data one day.
>
> And some days later the same query is run on the
> data, but some records have been added and
> subtracted.
>
> Is there a good method using access to compare
> the two tables?
>

On Wed, 22 Nov 2006 16:33:27 GMT, "tom" <(E-Mail Removed)>
wrote:

>Let us say that one runs a make table query on
>some data one day.
>
>And some days later the same query is run on the
>data, but some records have been added and
>subtracted.
>
>Is there a good method using access to compare
>the two tables?
>

Depends on the tables' structure. Is there a primary key one can use
to join the two?

There are third party tools such as Total Access Detective from FMS
(www.fmsinc.com) to do this, but they may be overkill...

This is just one of many reasons that I try to avoid maketable queries
- they're a recipe for storing "the same" data (which isn't really the
same) redundantly in two locations. If you have normalized tables
containing the (up to date and accurate!!) data, then you can use
Select queries as the source of a form, report, export, etc. without
this risk of anomalies.

John W. Vinson[MVP]

Basically, I just want to be able to compare
two different dynasets with the same fields.
I mentioned a maketable query to simplify
expressing the problem.

Using Unix this is a trivial problem. I could just
write the two sets of data to text files and use diff.
I am pretty certain that there are various other solutions
as well.

I am surprised that there is no easy solution in
Access for this fairly standard computer problem.


"John Vinson" <jvinson@STOP_SPAM.WysardOfInfo.com> wrote in message
news:(E-Mail Removed)...
> On Wed, 22 Nov 2006 16:33:27 GMT, "tom" <(E-Mail Removed)>
> wrote:
>
>>Let us say that one runs a make table query on
>>some data one day.
>>
>>And some days later the same query is run on the
>>data, but some records have been added and
>>subtracted.
>>
>>Is there a good method using access to compare
>>the two tables?
>>
>
> Depends on the tables' structure. Is there a primary key one can use
> to join the two?
>
> There are third party tools such as Total Access Detective from FMS
> (www.fmsinc.com) to do this, but they may be overkill...
>
> This is just one of many reasons that I try to avoid maketable queries
> - they're a recipe for storing "the same" data (which isn't really the
> same) redundantly in two locations. If you have normalized tables
> containing the (up to date and accurate!!) data, then you can use
> Select queries as the source of a form, report, export, etc. without
> this risk of anomalies.
>
> John W. Vinson[MVP]

use Access Data Projects and then CHECKSUM(*)

it works like a charm

-Larry


tom wrote:
> Basically, I just want to be able to compare
> two different dynasets with the same fields.
> I mentioned a maketable query to simplify
> expressing the problem.
>
> Using Unix this is a trivial problem. I could just
> write the two sets of data to text files and use diff.
> I am pretty certain that there are various other solutions
> as well.
>
> I am surprised that there is no easy solution in
> Access for this fairly standard computer problem.
>
>
> "John Vinson" <jvinson@STOP_SPAM.WysardOfInfo.com> wrote in message
> news:(E-Mail Removed)...
> > On Wed, 22 Nov 2006 16:33:27 GMT, "tom" <(E-Mail Removed)>
> > wrote:
> >
> >>Let us say that one runs a make table query on
> >>some data one day.
> >>
> >>And some days later the same query is run on the
> >>data, but some records have been added and
> >>subtracted.
> >>
> >>Is there a good method using access to compare
> >>the two tables?
> >>
> >
> > Depends on the tables' structure. Is there a primary key one can use
> > to join the two?
> >
> > There are third party tools such as Total Access Detective from FMS
> > (www.fmsinc.com) to do this, but they may be overkill...
> >
> > This is just one of many reasons that I try to avoid maketable queries
> > - they're a recipe for storing "the same" data (which isn't really the
> > same) redundantly in two locations. If you have normalized tables
> > containing the (up to date and accurate!!) data, then you can use
> > Select queries as the source of a form, report, export, etc. without
> > this risk of anomalies.
> >
> > John W. Vinson[MVP]

On 22 Nov 2006 15:25:08 -0800, "Larry Linson"
<(E-Mail Removed)> wrote:

>use Access Data Projects and then CHECKSUM(*)
>
>it works like a charm
>
>-Larry

Aaron Kempf, spoofing Larry.

John W. Vinson[MVP]

"Larry Linson" <(E-Mail Removed)> wrote:

>use Access Data Projects and then CHECKSUM(*)
>
>it works like a charm
>
>-Larry

Fraudulent posting not by Larry Linson.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm