Re: need to delete record having two different fields with same identical value

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: L. T. Portella (portella_at_NOSPAMoptonline.net)
Date: 05/14/04 

Date: Fri, 14 May 2004 04:49:42 GMT

I use the neat trick of <> and this solved my most pressing problem for
which I truly thank you.
No, there is nothing wrong with the database design; it is just the way
things were set up originally and which did not contemplate the present
snag. Once again many thanks
"Stephen Glynn" <stephen.glynn@ntlworld.com> wrote in message
news:2gh8r7F2ptl0U1@uni-berlin.de...

>
> Assuming you're always comparing the same two fields (Field1 and Field2)
> and that RecordID is the primary key, just write a query to show
> RecordID, Field1 and Field2, and put =[Field1] in the criteria box under
> Field2. Run the query to check it, and then turn it into a delete query.
>
> Sounds to me as if there's something wrong with the database design,
> though -- you shouldn't need to be deleting the rows if the database is
> properly normalised.
>
> Alternatively, which might be a lot safer (I hate deleting data unless I
> absolutely have to), use <>[Field1] as the criteria for Field2 and then
> base all your forms, reports and other queries on this query rather than
> on the underlying table. That way the records with duplicate fields
> stay there intact should you ever need them, but you don't get to see
> them unless you want to.
>
> Steve

Relevant Pages