Home Forums Discussions Problems RUN TIME ERRORS

ANYONE KNOW WHAT WE CAN DO TO FIX THE CONSTANT RUN TIME ERROR SHUTDOWNS?

Rarely we get that-

when we are in the chart, and I open Internet Explorer, to look up say some document- eg: Chiari malformation, to hand over to patient, some documents on Internet, when we open give this run time error, then AC closes. I dont know why.
When you open AC, it can resurrect the previous note, so you dont lose anything, but still an annoyance as you have to log in again.

I cant explain which docuements in internet gives that, but lately I am getting a feeling before I click that reference that I should not go that website, I should stick to -- say Mayo, Cleveland clinic, NIH, CDC-- those reputable names where if you open that docuement our AC will not shut down.

I dont know if this helps, but for me it happens only when I open certain documents on internet.

Just started using tablet PC. (I am a latecomer to tablet PC world). Because of default power settings, when I was doing a procedure the tablet turned off the hard disk, when I came back on after proceduure the wireless network was disconnected, without realizing that I moved the cursor from one field to another the guess what, I got run time error (I forgot the number- was it 51 or 53?? ) and AC closed.
I thought it was because of default power settings this happened, so after I was on network again, logged in, ressurected the old note and carried on.

Now of course the default power settings are changed to be on all the time. Just drains that battery.

When I bought Nancy her new tablet I also bought her an extra power pack for the main exam room. So now most of the day while she's in there she is always plugged in on wall power and NOT set up to go to a hard sleep while on the wall. We usually leave her other power pack set up at her desk, so if she is working there for a long time she can just plug in there as well. We almost never run out of juice or go to sleep unexpectedly. But we still get run-time errors sometime. I think Jon has mentioned that a loss of connection back to the main database can cause this, such a wireless glitch and that it doesn't always take much of a lapse either for this to happen.