Page 1 of 1
New case error
Posted: Mon Sep 17, 2018 3:59 pm
by EHCS
one of my practices all of a sudden can not create new cases. . I get error 7057 everytime I try and copy or create a case. then it creates a case without a # and won't let me delete it. It has assigned case #7 to both the cases it did create, it is like it is trying to assign case #7 to everthing and then cant so it errors out...the cases i have should be more like 2998 not 7.... IT was working fine on friday and now today it won't create cases. all of my other practices are creating cases just fine. Not sure why all of a sudden it is doing this. Any help would be appreciated.
Re: New case error
Posted: Mon Sep 17, 2018 4:08 pm
by EHCS
just a quick note I just created a new patient and it create a new case just fine, but it assigned her case #7 so now i have 3 case #7 for different patients and if I try and create an additional case for the same patient under a different provider it errors out because it is trying to assign case 7 again.....
Re: New case error
Posted: Mon Sep 17, 2018 5:14 pm
by EHCS
i just tried to copy a case and I got error 3111.....then it freezes
Re: New case error
Posted: Mon Sep 17, 2018 9:07 pm
by Gavin Walker
Make sure you have a backup and then pack and rebuild all indexes in File Maintenance. Then make sure you have the latest service pack installed for your version of Medisoft. If you get any errors doing either of these, then you probably have data corruption of some sort.
If you need our help performing a Medisoft data repair, then you can purchase that off our shopping cart here. If you have Medisoft v19 or older, then private message me for pricing.
Re: New case error
Posted: Tue Sep 18, 2018 10:33 am
by EHCS
is it a good idea to pack and rebuild indexes periodically?? I wasn't sure what that did exactly so I have never done that with any of my practices.
Re: New case error
Posted: Tue Sep 18, 2018 11:16 am
by Gavin Walker
I would do it along with recalculating all balances once per month before you send out patient statements.
Re: New case error
Posted: Wed Sep 19, 2018 1:33 pm
by Gavin Walker
When we got your data there were a few key columns that should have been auto-increment data type but were integer instead. I have seen this caused by some data repair utilities such as MediUtils Copy Data Tables or it can even be done in ARC32. Otherwise, not sure how this could have happened. There were several cases with duplicate case numbers so we had to renumber about a dozen of them throughout the database. Note, since this happened in the Case table, it could have lurked for a while before it became obvious it was a problem.