How To Prevent Duplicating Records When Importing Data
Oct 14, 2011
We are a travel company and I am just setting up a new database with two tables - [Client_Table] & [Enquiry_Table].
Most exisiting clients call in when they want to make a new enquiry so the 'user' can go it to a form which creates a 'new enquiry' for that client.
We also download 'new enquiries' from our website. This data includes info that goes in to the [Client_Table] and [Enquiry_Table]. They download in to a XL spreadsheet. Currently I copy and paste the data (not sure if there's a better way) from the XL speadsheet in to a query. This query creates a new client record & a new enquiry record which are both linked by a primary key [Client_ID].
This all works however the problem I have is that sometimes existing clients enquire through the website. They do fill in a field to say they're an existing client but if I paste them in to the query as explained above it creates a duplicate client record.
The only way around this I can think of is it to take out any exisitng clients from the XL spreadsheet first, search for their Client_ID and then paste these enquiries seperately with their Client_Id's in to different query which only adds a new record to the [Enquiry_Table] and links them to their exisitng record in the [Client_Table].
I have a main form with several continuous subforms. Each subform consists of several listbox controls. I would like to require the user to select an item from the listbox before being allowed to move to the next record in the subform, and upon reaching the last record in that continuous subform, to require an entry there in order to move to the first record in the next cont. subform.
As an added bonus, it would be nice, though not necessary, to automatically jump the focus from one record to the next after data is entered. But my basic goal is to avoid skipping records.
Caveat: I cannot use the "required" option in the field to which the control is bound because that field has a default value previously entered using an append query. (The default value basically means "not yet entered" and is not one of the options in the listbox. I am using this because this field is a foreign key in the table, thus it must have a value in order to have a record with which to populate the subform.)
My apologies if this has been asked and answered elsewhere, but I've searched and, while I found a few related threads, they don't quite answer my question. Here they are for reference:
Thanks for any help! Also, if you are going to recommend VB code, could you be specific about how and where I should use it? I'm not afraid of code, but I'm definitely new to it...
I'm building a database at work to see if we can replace some of the "buhzillion" spreadsheets we currently use to track data on sites and employees across the country. I've set up the primary excel tables the way I want to import them, but Access keeps converting my Employee Numbers (mostly 7 digit numbers, "text" format in excel) to scientific notation during the import process and then giving me errors because my primary key "EmployeeNumber" has duplicates. How do I tell Access to import these as text instead of numbers? I'd really like to not have to type in data for 100+ employees and over 1000 sites, you know?
I have a report for parking tickets. In the report is a subreport listing each violation on the parking ticket referenced on the report.
Everything works fine except for tickets with multiple violations. For example, some tickets with two violations come out correctly on the subreport (both violations listed). Others show one of the violations listed twice and the other violation not listed at all. The queries behind the report and subreport show the correct information without the duplications.
I'm able to import new data from excel just fine, but I can't import updated data from excel due to duplicates not being allowed for a particular field. Is there a way to keep from importing duplicate records based on one field, but still import data from other fields where the information is different from the excel file?
Here's another one I'm stumped on. What would be the best way to do this... if it can be done:
The tables in question are the following:
1. Exhibitors (stores exhibitor data, i.e. name, age, address, etc) 2. Livestock (stores livestock data for each exhibitor, i.e. breed, weight, gender) 3. Shows (stores data about each show, i.e. title, date, location)
I would like to have the Shows table to also store which exhibitors and livestock participated at this show. For example:
County Show: Jane Doe (exhibitor) - blackie, whitie (livestock) John Smith - spot, blue, cutie-pie James Black - smokey, sassy, fluffy
State Show: Jane Doe - blackie James Black - spot, blue, cutie-pie, snuffles Christy Meek - baby, apples
The problem is that each show will be associated with multiple exhibitors (and their different livestock). AND each exhibitor (and their livestock) will be associated with different and often times multiple shows.
So what would be the best way to have the Shows table pull the exhibitor and livestock data without having to duplicate exhibitor records for each show?
I created a database. exported some Excel data into Access tables, created a number of lookups, default values etc. and created a pretty simple query.
My problem is that after importing and tweaking the data, when I add new records, my queries do not pick them up! I have tried:
1. saving, closing, opening and re-running the queries. 2. putting an Nz expression for each field in the query as I read that null values may cause a problem. 3. wrote the query again, field by field to see if all records were received. 4. Exported the table back to Excel and imported to a new Access table in my database
I am creating a purchase request form for my company. The main form contains the PO Request # (autonumber) and general vendor and shipping information. The subform contains the item numbers on the order, the quantity and costs. What I am trying to do is make it so that users can click a "duplicate" button on the main form of an existing PO Request and have all the data replicated into a new PO Request. A lot of what we order is repetitious and it would time saving if users could just duplicate an order and modify as necessary. Can anyone help me with this one... Thanks!:confused:
Hello, I know it's against any database logic but I need a code behind a a button to copy data from one field to another. What I am trying to do is: I have a table with two fields: Father Last Name (txtFLN) Child Last name (txtSLN)
When writing my data to the table (I use a form named MASTER), I type the father's last name and would like a button that copies that same entry in the other field?
Okay, I've learned TONS from this forum alone as a self-taught database user. But now I'm in a rut... I created a query that contains the following fields:
Termination Date, Name, Rehireable?(yes/no), and age (if statement). This is the if statement someone helped me to write:
Ages: IIf([Age] Between 16 And 20,"16-20",IIf([Age] Between 21 And 25,"21-25",IIf([Age] Between 26 And 30,"26-30",IIf([Age] Between 31 And 35,"31-35",IIf([Age] Between 36 And 40,"36-40",IIf([Age] Between 41 And 45,"41-45",IIf([Age] Between 46 And 50,"46-50","Over 50")))))))
At first glance things looked fine but I checked again and the data is all duplicated - each employee is showing one record for rehireable (yes) and another record for non-rehireable (no).
I'm not even going to think about getting into this more until Monday, so if you have any insight on why my data is doubled I would REALLY appreciate it. Thanks!
I created a query using 2 tables, [tbl_transaction_details_b] and [Siemens_Contact_Info1]. Currently it is pulling 38 records (which is right and the same number of records in tbl_transaction_details_b). But when I add Line Number to the query (which is in [Siemens_Contact_Info1] I go from 38 records to 1019. Here is the SQL view before adding line number:
SELECT Siemens_Contact_Info1.[Mail Code], tbl_transaction_details_b.INVNUMBER, Format([INVDATE],"mm/dd/yyyy") AS InvoiceDate, "USD" AS InvoiceCurrency, Null AS [Canadian Tax Registration ID], tbl_transaction_details_b.PONUM, Null AS [Account No], Null AS [Payment Terms], tbl_transaction_details_b.SHIPTOCUSTOMERNAME, tbl_transaction_details_b.SHIPTOADDR1, tbl_transaction_details_b.SHIPTOCITY,
[code]....
What do I need to do in order to pull the line number for each record? Oh the line number is determined by the EQUIP_SEG which is also on [Siemens_Contact_Info1]
I have two tables that I'm struggling with how to relate to each other. One is tblHardware which contains all the items that we sell. There are no duplicates in this table. The only columns are a part #, description, long description, and cost.
Then I have another table with is tblPackages. These are the packages we sell which pull from tblHardware. This one just has an autonumber, description, and image (image I'll add later and not worried about now).
What I'm struggling with is how to tie these two together because one Package will contain multiple items from Hardware however there are multiple Packages that have the same Hardware items (17" monitor for example).
What is the best way to prevent widowed records? By widow record I mean records in the parent table that do not have a related record in the child table.
I have a tblOrder that is linked to a tblProductOrder by the OrderID field. I don't want the user to be able to create a record in tblOrder without adding some products to the order, which will be stored in tblProductOrder.
I have a database with several forms, tables, queries etc. and it works fine. One of the users of the database accidentally deleted a record which was displayed by a query. I have selected AllowDelections = No in all object properties. Despite this, the record got deleted. Is there a way to prevent such deletions? Kindly help.
I have a form, that once prompted, finds a certain record for the user. How do I prevent the user from being able to see any other records but that one, once the form is opened? The user needs to be able to edit the particular record they opened, without viewing or editing any other records in the database. Is there a way to hide the bar at the bottom of the form that allows users to manipulate through the different records?
I am using a data entry form to enter new data into one of the tables.How can we prevent entry of duplicate records? Duplicacy shall be checked on the first two fields only. Please help. regards bijon
Hello, I HAVE searched the forums for many days but I could not find a solution. Maybe I'm not sure what to look for...
The MAINFORM_1(single form view) is based on a Query and has a cbo named 'cbo_client'. This cbo is for a field named [client_id]. The AfterUpdate [event] of 'cbo_client' does a requery on a field in the the following SubForm:
In the SUBFORM_1(datasheet) (based on another Query) is another cbo named 'cbo_subclient', with a select statement of 'Select (all the needed fields) FROM tbl_subclient WHERE ((([tbl_subclient].[subclient_id])=[Forms]![mainform_1]![cbo_client])).
Everything (incl. the REQUERY) works fine, and all the tables gets updated with the records the way it should. No problems.
But this is where i get stuck...: Once the user has entered data in the SUBFORM_1 datasheet, and then >changes the 'cbo_client'< on the MAINFORM_1, it requery the subform like it should, BUT the previously entered data in the subform is already written to the table!
So, I need a way to prevent the data in the subform from beiing stored if the user changes the cbo on the mainform (for a second time). OR prevent the cbo on the mainform from beiing changed after the subform is completed.
I hope you understand what I'm trying to do...
Please, just a point in the right direction and i'll battle it out from there.
I have a form that is opened by the following code: Private Sub Status_AfterUpdate() If Status.Value = "WIP - Snagged" Or Status.Value = "WIP - Suspended" Then DoCmd.OpenForm "NotesJobChanged", , , acFormAdd Forms!NotesJobChanged!txtJobNo.Value = Me!txtJobNo.Value Forms!NotesJobChanged!Date.SetFocus End If
This 'NotesJobChanged' form has three text boxes on it - JobNo, Date & Note. The JobNo is autofilled from the code above. If nothing is entered into the other fields and the form is closed this record is entered into the database with only the JobNo filled in.
What I want is a way to force the user to enter data into these fields. I don't want to set the 'Required' property of the field to yes as it generates an awful system error message. If the user attempts to close the form without filling it out can they be reminded that they have to, but with an option then to close the form if they really don't want to enter any data? If they do chose to close without filling it out can it be prevented from being added to the database.
the proper code to prevent duplicate records in my form?
I'm using:
Private Sub Ctl_Lname_BeforeUpdate(Cancel As Integer) Dim dupCount As Long dupCount = DCount("*", "Clients", "[LastName]= '" & Me.[LastName] & "'" & " And " & "[PreferredName] = '" & Me.[PreferredName] & "'") If dupCount <> 0 Then Beep MsgBox
[code]....
"This name already exists in the database. Please check that you are not entering a duplicate person before continuing.", vbOKOnly,
I'm learning how to do Many to Many relationships and I think I've got the basic idea down, I am just not sure how to prevent the same 2 records from being associated twice.
For example:
My practice database deals with Authors and Books.
I was able to set it up so that Mike Gunderloy and Susan Harkins are both Authors of the book: "Upgrader's Guide to Microsoft Office System 2003".
I was also able to set it up so that Mike Gunderloy and Susan Harkins are both Authors of the book: "Automating Microsoft Access 2003 with VBA".
The thing I want to prevent is something like this:
Book: - Automating Microsoft Access 2003 with VBA
Authors: - Mike Gunderloy - Susan Harkins - Susan Harkins (Duplicate)
Good morning! I'm building a database for use by four technicians in a call-center type operation. The call records are purely transactional in nature -- once the call has been logged, the record is closed. If the customer calls again, a new record is opened.
The supervisor doesn't want the techs to be able to go back and edit a record once it's entered -- the records are for quality-control purposes and he doesn't want them gaming the system by going back and changing things after the initial call is logged (let's not discuss the issue of employee psychology, motivation, Office Space, etc.). So I'm trying to figure out how to do that; they all have wheel mice, and I can currently see all the records as I scroll back and forward with my mouse wheel, so I'm assuming they'll be able to, as well.
