Re: DBEngine .Execute Method Fail Scenarios

"david" <david@xxxxxxxxx> wrote:

circumstances (if you know you're appending a recordset that has
duplicates that you know for certain you want to discard), but is

Which is a bad idea because the process is slow and causes database bloat.

And it consumes autonumbers. Which is not a big deal nevertheless I
have some pride in my craftmanship. <smile>

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
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
.

Relevant Pages

  • Re: DBEngine .Execute Method Fail Scenarios
    ... duplicates that you know for certain you want to discard), ... database bloat. ... usenet at dfenton dot com http://www.dfenton.com/DFA/ ...
    (microsoft.public.access.modulesdaovba)
  • Re: DBEngine .Execute Method Fail Scenarios
    ... duplicates that you know for certain you want to discard), ... database bloat. ... And it consumes autonumbers. ...
    (microsoft.public.access.modulesdaovba)
  • Access Append Query Failure
    ... "Microsoft Access can't append all records in the append query... ... it does not show any duplicates. ...
    (microsoft.public.access.queries)
  • Re: DBEngine .Execute Method Fail Scenarios
    ... Whereas I strongly suspect you and I would go to great lengths to not ... add those duplicates in the first place so we wouldn't get the ... Tony Toews, Microsoft Access MVP ...
    (microsoft.public.access.modulesdaovba)
  • Re: Duplicate query
    ... "Running Microsoft Access 2000" ... "juan" wrote in message ... > query it will not do this, either with the find duplicates. ...
    (microsoft.public.access.queries)