[AccessD] deduplication

John,

take a look at cursors.
They operate like recordsets do in Access.

If you know how to do it in Access with a
recordset, you can do the same with a cursor
in SQL Server.

Robert

At 11:16 AM 1/15/2007, you wrote:
>Date: Mon, 15 Jan 2007 07:46:14 -0500
>From: "Michael R Mattys" <mmattys at rochester.rr.com>
>Subject: Re: [AccessD] deduplication
>To: "Access Developers discussion and problem solving"
>         <accessd at databaseadvisors.com>
>Message-ID: <007301c738a3$255dafb0$0302a8c0 at default>
>Content-Type: text/plain; format=flowed; charset="iso-8859-1";
>         reply-type=original
>
>----- Original Message -----
>From: "JWColby" <jwcolby at colbyconsulting.com>
><snip>
> > Thus my job is to now identify all three of these "john Colby" records and
> > merge all of the "survey" fields back into a single record, deleting the
> > two
> > now un-needed extra records in the process.  If it weren't for the fact
> > that
> > there are about 650 "survey" fields this would not be such a big task.
><snip>
> > It is specifically the ~650 fields that causes the issue for Access as (I
> > believe) Access cannot handle that many fields at a time.
><snip>
>
>I think I'd still look at how to normalize the database.
>Look at how to query the data such that an INSERT ...WHERE
>would create a distinct table for Survey N.
>Then write all 700 fields as the header to a csv
>Then use each survey-query to populate the one line across.
>Import into a new table when finished.
>
>Michael R. Mattys
>MapPoint & Access Dev
>www.mattysconsulting.com