Preventing duplicate data?
Here is my problem, it's looking kind of complicated to me, but maybe it's because I've confused myself. so i need an outside opinion. (that's you guys)
I have this data, which is from testing a device. this data, which can be rather extensive, is written into a comma delimited text file.
What I am doing, is taking said text files and importing them into access using my vb code, and then doing queries and all that good stuff on the data, to eventually manipulate it into an output excel document.
but, what I am doing right now in this, is trying to prevent duplicate data.
Is there a way I can do this BEFORE inserting the data into the database?
check the data to be imported vs. the existing data?
There should never be duplicate data (start times, part numbers, serial number and whatnot), UNLESS the user has retested a device and wants to keep both sets of data.
Right now I'm kind of unsure about HOW I want to test the data, or govern what constitutes duplicate data.
But is there a way to test before the insertion?
like treat the text file like a database, and do a normal sql query on it to see if the first entries match (make sure same file is not imported twice), or something along those lines?
I think I've just really mixed myself up, haha.
Any suggestions on how to go about this?
Visual Basic 6.0
Microsoft Access 2003
By Kathleen Dollard in forum .NET
Last Post: 05-03-2002, 12:10 AM
By Peter Prager (Canam Software) in forum vb.announcements
Last Post: 08-15-2001, 10:48 AM
By Tim Frost in forum xml.announcements
Last Post: 04-02-2001, 10:53 AM
By Dale in forum VB Classic
Last Post: 06-21-2000, 06:44 PM
By William Gaddam in forum VB Classic
Last Post: 05-02-2000, 09:19 PM
Top DevX Stories
Easy Web Services with SQL Server 2005 HTTP Endpoints
JavaOne 2005: Java Platform Roadmap Focuses on Ease of Development, Sun Focuses on the "Free" in F.O.S.S.
Wed Yourself to UML with the Power of Associations
Microsoft to Add AJAX Capabilities to ASP.NET
IBM's Cloudscape Versus MySQL