"never say never...": Except in one instance I can think of. You are assuming that the note in question is saved on the main computer. But the note may be lost on the client computer if it was never successfully sent to the server machine in the first place. (A-HA!)
"Peter, can you explain...": Yes. I am distinguishing between saving to the database (which should only happen on the main computer) and the user interface being updated. I can add to the database all I want; that does not mean that the user interface reflects these changes.
I had AC UI open on the client computer, and open also on the main computer. I added a new patient to the UI on the client computer and added a new patient visit note in the UI on the client computer. I do not know at what point these changes are saved to the SQL database. I finished my note and was at the schedule/search screen on the client machine. I then went over to the main computer and looked at the list of patients and this did not include the new patient.
Now, in retrospect, I can understand if you are now to tell me: well obviously he does not show in the list. That was a search done previously. To see the new patient you have to refresh the search list (of all patients).
and that is what I did. I refreshed the search list on the main computer in the AC window and the new patient popped up.
I guess it would be nice if any changes to the SQL database from one network computer would signal the other machines on the network to reload the database. On the other hand, one could argue (true or not, I do not know) that this may slow things up too much.
Chew on that and tell me how it tastes Bert.
