Can someone tell me what's wrong with my update query?

[tanyalee123]

Monthly I have to append new patients to my DB. That all goes as planned, but I also want to update any changes in the patient's address, phone, last name, etc, so I created an update query to be run after the append query. However, when I run the query in my test DB, it wants to make an update to the DB of every record that has a corresponding record in the spreadsheet (HP) that I'm using to run the update. I know for sure that this can't be right - everyone can't have had an update to their demographic data. I don't understand why it wants to update every record...



Hopefully you can see the image.

Here is the SQL:
UPDATE HP INNER JOIN PatientInfo ON HP.UniqueID = PatientInfo.UniqueID SET PatientInfo.PropertyName = [HP].[PropertyName], PatientInfo.Plan = [HP].[Plan], PatientInfo.LastName = [HP].[LastName], PatientInfo.Address = [HP].[Address], PatientInfo.City = [HP].[City], PatientInfo.State = [HP].[State], PatientInfo.Zip = [HP].[Zip], PatientInfo.Phone = [HP].[Phone], PatientInfo.Lang = [HP].[Lang];

Thanks!!
Tanya

[June7]

The query will only update those records in PatientInfo that have a match in HP.

Shouldn't really matter if it runs against every record. If their data is unchanged then the update will just update with the same data. If you do want to limit the update then need filter criteria.

HP is a linked spreadsheet or is it a native table that records are imported into from spreadsheet? Why have another table for the PatientInfo?

[tanyalee123]

Thank you, it was freaking me out that it was showing that many updates. I'm fine with that.

HP is a linked spreadsheet that I get from our Analytics department monthly, but it doesn't contain every record in the database. When a patient's health insurance terminates, they won't be on the spreadsheet anymore, so I use the spreadsheet to add new patients and to update their health insurance term date.