We have recently upgraded to v6.26.2.286 after moving the database onto an in-house server. Whilst manually checking a number of records, it was found that a large number of records that previously had the determination 'observation' and had passed verification are now displaying a 'not verified' flag! At the moment it only seems be those records with the 'observation' determination that are affected but this could possibly change as I investigate further. Is there a means of pulling out all those records to check whether or not this is the case and to change back their verification flag accordingly? Manually going through 1.8m records to root out the offenders will be an impossible task if not!

I would be interested to know how and why this has occurred as it has obvious implications when it comes to reporting. I hope that I have explained the situation clearly enough to determine a/the cause. If not, please ask specific questions and I'll try to answer.

Thanks,

Paul

EDIT: Having used the wizard to report on a number of known checked but unverified records, applying all four combinations of the two constraints 'exclude unchecked data' & 'exclude failed/pending verification data' in the complex filter, all of the records were extracted in all instances! Is this an issue allied in some way to the above? Surely it shouldn't happen?!!