In my experience, the best fix is to upgrade to a more robust database solution
(yes, this is not a quick fix when you are not the developer)
Access is simply a poor solution for networked, multi-user databases, as anyone
of us who has similar setups has realized.
Mo’ users, Mo’ problems.
-sandor
On Feb 23, 2018, at 8:43 AM, David Bennett <david.bennett@xxxxxxxxxxxxx>
wrote:
We have been having a rash of random database crashes on
our Spectralis. This is happening 1-2 times a week. Recently 3 times in one
day. Heidleberg has been very helpful logging on and rapidly correcting the
database. This is on a network. The servers have been tested. We have had all
the lines tested both input and output as suggested by Heildleberg. We are
making sure the machines are shutdown properly, workstations closed out
properly and data properly archived.
Having the database randomly corrupt is annoying
especially during heavy clinic use because it shuts down all the capture
stations and all the workstations across both campuses. At times I cannot get
into Heidleberg quickly causing us to reschedule patients while Heildleberg
system is down. Obviously the database fix is an easy one since it takes no
longer than 5 -10 minutes to get us back up and running. I recently asked
Heidleberg to tell me how to correct the Access database since we cannot seem
to find the cause of the corruption . Their response was he was “reluctant”
to give their fix it to me.
Has any other users had similar database corruption
issues? Did you isolate where the issue was? How was it solved? Any help here
or offline would be appreciated.
David B. Bennett
VCUHealth System
Virginia Commonwealth University
Department of Ophthalmology
Richmond, VA
david.bennett@xxxxxxxxxxxxx
