Append Query

[Guest]

Is there a max # of records I can append to a table using an append query?

Also, I thought the max # of records in an Access database was 65,000. I
have two separate geodatabases (mdb extension) created by ESRI/ArcGIS. Each
geodatabase has approx. 1,443,585 records.

I want to compare the two tables for duplicates. I thought the best way to
do this would be to combine the two existing tables into one new table and
then search for a duplicate in the new table.

I am getting an "Invalid Argument" error when I run the query. I know this
has to do with the table size. I have tried only appending 59,999 records
(OBJECTID < 60000) but I still get the same error.

What is the max # of records I can append? I am sure there is a setting in
the registry that can be changed.

Or, is there another solution besides puttng these tables into Oracle? I
know Access, not Oracle.

I am running Access 2003, OS is XP Professional, Dell Optiplex GX280.

Thanks in advance.

Andrew

 

[MGFoster]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

The maximum size of an Access db (2002, at least) is 2 gigabytes. Is
your db that big?

You have to have a LOT of RAM to do what you're proposing.

What does your SQL look like. Perhaps you could use a LEFT JOIN to find
records in one table that are/aren't in the other.

Perhaps, you could remove the duplicates from one table at a time, then
compare the 2 "cleaned" tables for records in one that are/are not in
the other.

There are various ways to clean up your data. How are you doing it?
--
MGFoster:::mgf00 <at> earthlink <decimal-point> net
Oakland, CA (USA)

-----BEGIN PGP SIGNATURE-----
Version: PGP for Personal Privacy 5.0
Charset: noconv

iQA/AwUBQnKwMoechKqOuFEgEQLUhgCZAXXi+DKuk9qhO2BMfz24vSHhn9cAoNSj
jTZOV+0tA8LzsKCA0C1NbTfW
=YkZY
-----END PGP SIGNATURE-----

 

[Guest]

Yep, 2,095,044 KB for one and 2,095,1087 for the other

I have not written any SQL. i was just trying to use the standard approach
to doing an append query: make a select query, change it to an append query,
etc., etc.

There are no duplicates in the individual tables. I think one table may
have some of the records from the other table and vice versa. Eventually, I
need to get these into one table but I do nto want to do so if I know in
advance the tables are duplicates of each other or that they contain
duplicate info.

I have not cleaned my data yet. I want to 1st make sure the two tables do
not have some of the same info in them.

Andrew

 

[MGFoster]

Yep, 2,095,044 KB for one and 2,095,1087 for the other

I have not written any SQL. i was just trying to use the standard approach
to doing an append query: make a select query, change it to an append query,
etc., etc.

There are no duplicates in the individual tables. I think one table may
have some of the records from the other table and vice versa. Eventually, I
need to get these into one table but I do nto want to do so if I know in
advance the tables are duplicates of each other or that they contain
duplicate info.

I have not cleaned my data yet. I want to 1st make sure the two tables do
not have some of the same info in them.

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Since the 2 tables are in 2 separate .mdb files you can compare the
tables - just link one table to the other's .mdb file. Then run queries
on the 2 tables. You will still require a lot of RAM to run these
queries (2 gigs would be great, probably be acceptable w/ 1 meg). And
DO NOT do this on Windows 98 - use, at least, Windows NT 4.0 SP3 (4?).
Good Luck.
--
MGFoster:::mgf00 <at> earthlink <decimal-point> net
Oakland, CA (USA)

-----BEGIN PGP SIGNATURE-----
Version: PGP for Personal Privacy 5.0
Charset: noconv

iQA/AwUBQnK2VoechKqOuFEgEQIvewCff/7OEzfNoLeEgBWZsj1orTjMI3oAnjK+
pcnx3YV91K3ahZ+2U9KBkjnK
=dcvG
-----END PGP SIGNATURE-----