MLH,
I think what you're after is a way to delete the *duplicate* entries but
still retain the *origonals*. I.e. keep ONE (and only one) version of every
unique record. This is a problem I have tried to address several times and
never come up with a 'one-step' solution. I think what Bob is suggesting
will blow away ALL records that have duplicates, which I'm guessing is not
what you want.
Sound reasonable? Ideas, anyone?
Simon
"Bob Quintal" <rq******@sympatico.ca> wrote in message
news:Xn**********************@207.35.177.135...
MLH <CR**@NorthState.net> wrote in
news:04********************************@4ax.com:
I never quite figured out how to reconfigure it to automatically
delete redundant entries. Of course, one cannot always blatantly
blow redundant records away w/o regard to which one it is that
you wish to keep. But, sometimes you can. Anybody developed
anything like this?
(used powrmail tblEFaganReps) ==> ignore personal alzheimer note
You don't reconfigure it. You do create a delete query and use this
one as its datasource.
--
Bob Quintal
PA is y I've altered my email address.