[AccessD] Fastest Way

Rocky Smolin rockysmolin at bchacc.com
Fri Jan 15 10:21:29 CST 2010


I like it!  But I still have to import to a temp table because there is
other error checking that must be done on a record in addition to checking
for dupes. 

R 

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Max Wanadoo
Sent: Thursday, January 14, 2010 11:45 PM
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] Fastest Way

I don't understand what you mean by brute force or findfirst.

Just create  the unique index on the 5 fields on your existing table.  You
only need  do this  once.

Then import using transfer method with on error routine in place.

If errors out on 3024 (or whatever the dupe record err No. is - this is air
code)
Then just resume next

That's it.  No findfirst  or anything.  The transfer method will import each
record. If a  dupe exists it will go to the error routine where it will be
told to resume the input.


Max


-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Rocky Smolin
Sent: 14 January 2010 23:56
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] Fastest Way

That was my first thought - brute force - time is not that critical.  And it
would only be a couple of lines of code additional in the current import
routine - just a .FindFirst.  If later it turns out that the time is
unacceptable, I could bail to the other approach.  Still thinking.... But
with the brute force method I could quickly set up a test case.  I already
put start time, end time, and elapsed time test boxes on the form.  

Rocky


-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Max Wanadoo
Sent: Thursday, January 14, 2010 1:36 PM
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] Fastest Way

It's a done deal.  If you want speed and efficiency,  then go  my way.

Unique index on relevant fields.  Let access handle the dupes.  One read-One
input-Finito.

Max


-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Heenan, Lambert
Sent: 14 January 2010 21:22
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] Fastest Way

I think we'd all be interested to know what method you eventually use, and
how the performance is.

Lambert 

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Rocky Smolin
Sent: Thursday, January 14, 2010 1:33 PM
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] Fastest Way

Actually don't want to delete and import - just bypass the incoming records
that are already in the table.

R 

--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com

--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com

--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com

--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com




More information about the AccessD mailing list