If ur SQL supports unique indexes (I don't know why it wouldn't) u can let it take care of the unique records problem. Decide what fields constitute a "unique record" and make that a primary key, the database won't allow those records to be duplicated. Then all u have to do is fire everything u've got into the database and let it take care of the rest.
At 02:22 PM 4/11/05 -0400, Craig Cardimon wrote: >I will need to compare strings to ensure that records I am inserting >into our SQL Sever 2000 database are not duplicates of records already >there. -- REMEMBER THE WORLD TRADE CENTER ---=< WTC 911 >=-- "...ne cede males" 00000100 _______________________________________________ Perl-Win32-Users mailing list Perl-Win32-Users@listserv.ActiveState.com To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
