"You can't assign a value to this object" error
The CCMDB.accdb will sometimes crash with the following error:
This usually happens if there is either
- an error on the first patient opened
- an error in the first patient filtered to, i.e. the first "complete" patient
- Error was re-reported by Con 2013-06-09: in her case error msg was title "Microsoft Office Access", msg "You can't assign a value to this object. - Patient 9745"; Con said that this is happening a lot for others, especially Gail, but just started for her. Ttenbergen 16:23, 2013 July 4 (CDT)*** happened today ON S4 laptop 7/5/13
- Still happening fairly regularly on my laptop but I just press end and ignore it.--CMarks 12:20, 2014 December 18 (CST)
- Still happens a lot but I just continue to ignore it.--CMarks 08:06, 2015 June 26 (CDT)
- I see this a lot as well, but just press end and ignore it~~
- yes happened yesterday but I press end and ignore as well, will snap shot next time Lisa Kaita 07:46, 2015 June 27 (CDT)
- I see this a lot as well, but just press end and ignore it~~
- Still happens a lot but I just continue to ignore it.--CMarks 08:06, 2015 June 26 (CDT)
Quick and dirty fix
One of the main causes for this error seems to be the ICU Var 2 - BRR check.
Error on first patient opened
If you are collecting on a PDA, review the data for the first patient and check to see if there are any obvious errors; if sofix them on the PDA. Otherwise, make a "fake patient" with a serial number 1 and enter a minimum data set for the patient. This will mean that the first patient opened doesn't give an error, and the next patient on the list will display errors properly rather than crashing.
Error on first filtered patient
Navigate to the patient without the filter and correct the error.
Background
Problem is caused by the error checker trying to set fields in a form to yellow before the form is fully opened. This is due to the chronological order in which events are run. The event that triggers the checks has to be right as the form opens, and at this point, the event that causes this is before the form finishes opening. Tina is not sure how to fix this problem at this time, hence the work-around above.