Duplicate Record Value

[eniola231Participant]

Hello,
I have been trying to access one of my patients record, every time I attempt , a dialogue box with a your caution says ” A record already exist with the value ‘per, 1060511180833163969’ . Please enter a unique value for this record.

[WilliamKeymaster]

Hi Eniola

Sorry to hear of the issues you have been having. If you have not already done so, please run a check and repair on the database to see if this resolves the issue. The steps on how to do this are listed via the link below.

https://pioneersoftware.co.uk/forums/topic/faq-324-what-to-do-if-your-database-becomes-corrupt?view=all

If you are still having problems after this then we will need to take a look at your database and give you instructions on how to upload it to us.

Please let us know how you get on.

[eniola231Participant]

Hello, am still having the same problem. I have done check and repair but the problem still remains

[Joshua BarrsKeymaster]

Hi,

Sorry to hear you are still having issues. As my colleague mentioned, you will need to upload a copy of your database to us so that we can take a look for you. To do this, please click the link below, and follow the instructions.

https://pioneersoftware.co.uk/forums/topic/faq-301-how-do-i-upload-my-database-to-your-ftp-server

[eniola231Participant]

The link specified is on how to use the consent manager

[WilliamKeymaster]

Sorry about that Eniola. Please find the correct link below.

https://pioneersoftware.co.uk/forums/topic/faq-301-how-do-i-upload-my-database-to-your-ftp-server

[eniola231Participant]

Hello William,

Find attached the error encountered during data upload[attachment=0:3o31ur9o]82BC50AF-349E-47AD-9ACA-BBF9937951C3.jpeg[/attachment:3o31ur9o]

[eniola231Participant]

File has been successfully uploaded, find attached image
[attachment=0:owi910j5]15BA7E70-1E4D-4F90-B1B4-FCE6949E5342.jpeg[/attachment:owi910j5]

[WilliamKeymaster]

Thanks for uploading that to us Eniola. To fix this issue, please try the following below.

– Go to the Tools menu in ClinicOffice
– Click the Advanced DB Operation button
– Please remove any text present in the database operation window
– Copy and paste the text in below

update per set per.id=1060511180833163968 where per.id=1060511180833163969

– Please make sure that the checkboxes “Can Adjust SQL” and “As Administrators” are ticked
– Click the Execute button
– Click the OK and then Close

You will need to refresh the patient grid after doing this, but you should find that you can now open the patient’s record.

[eniola231Participant]

Thanks, I can now open the patients record. Please is this operation suppose to wipe the patients data? As I can’t seem to see his previous stored records. (Financial, appointments e.t.c)

[eniola231Participant]

Hello Williams,
The patients financial record is missing, all records of previous appointments is also missing. How can I restore them.

[SupportKeymaster]

You will also need to update all references to that patient record. Please follow these instructions…

– Go to the Tools menu in ClinicOffice
– Click the Advanced DB Operation button
– Please remove any text present in the database operation window
– Click SELECT ALL to copy and paste the code below into ClinicOffice

update sms_in set per_id=1060511180833163968 where per_id=1060511180833163969;

update app set per_id=1060511180833163968 where per_id=1060511180833163969;

update appwait set per_id=1060511180833163968 where per_id=1060511180833163969;

update cas set per_id=1060511180833163968 where per_id=1060511180833163969;

update doc set per_id=1060511180833163968 where per_id=1060511180833163969;

update fileatt set per_id=1060511180833163968 where per_id=1060511180833163969;

update custom_patient_fields set per_id=1060511180833163968 where per_id=1060511180833163969;

update img set per_id=1060511180833163968 where per_id=1060511180833163969;

update inv set per_id=1060511180833163968 where per_id=1060511180833163969;

update inv set patient_per_id=1060511180833163968 where patient_per_id=1060511180833163969;

update alloc set per_id=1060511180833163968 where per_id=1060511180833163969;

update item set supplier_per_id=1060511180833163968 where supplier_per_id=1060511180833163969;

update link set ref_per_id=1060511180833163968 where ref_per_id=1060511180833163969;

update link set ref_cn_per_id=1060511180833163968 where ref_cn_per_id=1060511180833163969;

update pay set per_id=1060511180833163968 where per_id=1060511180833163969;

update per set refby_per_id=1060511180833163968 where refby_per_id=1060511180833163969;

update per set gp_per_id=1060511180833163968 where gp_per_id=1060511180833163969;

update per set resp_per_id=1060511180833163968 where resp_per_id=1060511180833163969;

update per set insurance_per_id=1060511180833163968 where insurance_per_id=1060511180833163969;

update per set invrecip_per_id=1060511180833163968 where invrecip_per_id=1060511180833163969;

update per set familyhead_per_id=1060511180833163968 where familyhead_per_id=1060511180833163969;

update po set supplier_per_id=1060511180833163968 where supplier_per_id=1060511180833163969;

update sess set per_id=1060511180833163968 where per_id=1060511180833163969;

update staff set per_id=1060511180833163968 where per_id=1060511180833163969;

update visnote set per_id=1060511180833163968 where per_id=1060511180833163969;

update credit set per_id=1060511180833163968 where per_id=1060511180833163969;

update pclog set per_id=1060511180833163968 where per_id=1060511180833163969;

update custom_session_fields set per_id=1060511180833163968 where per_id=1060511180833163969;

update custom_case_fields set per_id=1060511180833163968 where per_id=1060511180833163969;

update folder set per_id=1060511180833163968 where per_id=1060511180833163969;

update perpasswd set per_id=1060511180833163968 where per_id=1060511180833163969;

update recall set per_id=1060511180833163968 where per_id=1060511180833163969;

update custom_contact_fields set per_id=1060511180833163968 where per_id=1060511180833163969;

update company set primary_per_id=1060511180833163968 where primary_per_id=1060511180833163969;

update actlog set per_id=1060511180833163968 where per_id=1060511180833163969;

update ticket set per_id=1060511180833163968 where per_id=1060511180833163969;

update charge set patient_per_id=1060511180833163968 where patient_per_id=1060511180833163969;

update charge set invto_per_id=1060511180833163968 where invto_per_id=1060511180833163969;

update auxper set master_per_id=1060511180833163968 where master_per_id=1060511180833163969;

update cardsave set per_id=1060511180833163968 where per_id=1060511180833163969;

update hc_claimdefaults set per_id=1060511180833163968 where per_id=1060511180833163969;

update worldpay set per_id=1060511180833163968 where per_id=1060511180833163969;

update peracc set per_id=1060511180833163968 where per_id=1060511180833163969;

update sms_out set per_id=1060511180833163968 where per_id=1060511180833163969;

update consent2per set per_id=1060511180833163968 where per_id=1060511180833163969;

update consent2per_audit set per_id=1060511180833163968 where per_id=1060511180833163969;

– UNTICK the “Can Adjust SQL” box and TICK “As Administrator”
– Click the Execute button
– Click the OK and then Close

[eniola231Participant]

Thanks, problem solved , kindly advice on how to prevent reoccurrence in the future.

Regards

[Joshua BarrsKeymaster]

Thanks for your post.

We would recommend taking daily backups of your database, so that in the event of a database corruption, data can easily be restored with minimal loss.

 

[Author]

Posts