Conversion from v12 to v20 problems

Technical problems with Medisoft.
Post Reply
ardu
Posts: 35
Joined: Fri May 29, 2015 1:50 pm

Conversion from v12 to v20 problems

Post by ardu » Fri May 29, 2015 2:05 pm

I am trying to convert the v12 MediData to v20. I have tried clearing out appointments with repeat days but still get the following errors:

Conversion began at: 5/29/2015 12:40:33 PM
Converting from version v12 with conversion version: 20.0.2.68

Version 14 Conversion Log
Version 14 SP1 Conversion Log
Version 15 Conversion Log
Version 16 Conversion Log
Version 17 Conversion Log
Version 18 Conversion Log

Updating OHAPP Table had an error.
EADSDatabaseError: cpQryConvert: Error 7200: AQE Error: State = HY000; NativeError = 5132; [iAnywhere Solutions][Advantage SQL][ASA] Error 5132: The specified database object name is not valid. The specified field is not part of the table.
EXECUTE PROCEDURE sp_ModifyFieldProperty ( 'OHAPP',
'RepeatID', 'Field_Default_Value',
'0', 'APPEND_FAIL', 'OHAPPfail' );

Updating OHAPP table failed.
Updating OHRPTOLD Table had an error.
EADSDatabaseError: cpQryConvert: Error 7200: AQE Error: State = HY000; NativeError = 5132; [iAnywhere Solutions][Advantage SQL][ASA] Error 5132: The specified database object name is not valid. The trigger is not part of the database. ** Script error information: -- Location of error in the SQL statement is: 106 (line: 3 column: 12)
IF EXISTS (SELECT * FROM system.triggers
WHERE (NAME = 'OHRPTUPDATE_AUDIT')) Then
DROP TRIGGER OHRPTOLD.OHRPTUPDATE_AUDIT;
ENDIF;

IF EXISTS (SELECT * FROM system.triggers
WHERE (NAME = 'OHRPTDELETE_AUDIT')) Then
DROP TRIGGER OHRPTOLD.OHRPTDELETE_AUDIT;
ENDIF;

IF EXISTS (SELECT * FROM system.triggers
WHERE (NAME = 'OHRPTINSERT_AUDIT')) Then
DROP TRIGGER OHRPTOLD.OHRPTINSERT_AUDIT;
ENDIF;

Updating OHRPTOLD table failed.
Conversion had errors.
Conversion finished at: 5/29/2015 12:52:53 PM
----------------------------------------------------------------------------------

Any help on converting v12sp2 data to v20 would be appreciated. I assume there is a few steps in the conversion process I am missing. Is assume based on the first error there is a table that is in v12 OH data that is not in newer versions. I just do not know what data to remove so the conversion will complete.

Andrew
Posts: 153
Joined: Tue Mar 19, 2013 3:24 pm
Location: Springfield, MO
Contact:

Re: Conversion from v12 to v20 problems

Post by Andrew » Fri May 29, 2015 2:54 pm

I would run file maintenance on the data in v12. Go to File>File Maintenance, run all option on rebuild indexes and pack data. Then try converting to v19 before going to 20.
Andrew Analla
Support Team
MedTech Medical Management Systems
3058 S Delaware Ave
Springfield, MO 65804
Ph: 417.890.6777 | Fax: 417.890.6788

ardu
Posts: 35
Joined: Fri May 29, 2015 1:50 pm

Re: Conversion from v12 to v20 problems

Post by ardu » Fri May 29, 2015 3:20 pm

I performed the file maintenance as suggested. Same error when converting. I do not have access to the v19 conversion tool. I only have v20. Do I need to use the v19 conversion tool first, then v20?

Andrew
Posts: 153
Joined: Tue Mar 19, 2013 3:24 pm
Location: Springfield, MO
Contact:

Re: Conversion from v12 to v20 problems

Post by Andrew » Fri May 29, 2015 3:35 pm

Correct you can download the MS19 from our site. http://www.medtechsys.net/medisoft/service-packs/#m19sp. Download MS19 and open the data, it will convert. Then uninstall 19 and revenue management from the programs and features as well as deleting the Medisoft folder where it was installed to. Then install v20 and convert.
Andrew Analla
Support Team
MedTech Medical Management Systems
3058 S Delaware Ave
Springfield, MO 65804
Ph: 417.890.6777 | Fax: 417.890.6788

ardu
Posts: 35
Joined: Fri May 29, 2015 1:50 pm

Re: Conversion from v12 to v20 problems

Post by ardu » Sat May 30, 2015 9:35 am

Thank you very much. That did it. Having data conversion be convoluted and complicated is extremely frustrating.

Lastly, is it necessary to perform the Audit Records conversion?

User avatar
Gavin Walker
Posts: 4139
Joined: Wed Apr 04, 2007 10:11 pm
Location: Springfield, MO
Contact:

Re: Conversion from v12 to v20 problems

Post by Gavin Walker » Mon Jun 01, 2015 8:10 am

I would convert the audit records only if you discover you need them. I have yet to run across anybody that discovered they needed them. You can always run the audit conversion utility later, if necessary. Depending on the speed of your computer and the size of your data, the audit conversion utility can take days to run.
Gavin Walker
Walker Tek Solutions, LLC
417-890-6777

caramel25
Posts: 12
Joined: Wed Jul 20, 2016 2:29 pm

Re: Conversion from v12 to v20 problems

Post by caramel25 » Wed Jul 27, 2016 10:49 am

I have v18 and my problem is that my files from v17 won't convert because my newest version does not have the conversion featured in it. Is there a way to install extra software to make it possible to transfer my files from v17

Andrew
Posts: 153
Joined: Tue Mar 19, 2013 3:24 pm
Location: Springfield, MO
Contact:

Re: Conversion from v12 to v20 problems

Post by Andrew » Wed Jul 27, 2016 11:58 am

Sounds like you may have the V18 Demo and not the actual program.
Andrew Analla
Support Team
MedTech Medical Management Systems
3058 S Delaware Ave
Springfield, MO 65804
Ph: 417.890.6777 | Fax: 417.890.6788

User avatar
Gavin Walker
Posts: 4139
Joined: Wed Apr 04, 2007 10:11 pm
Location: Springfield, MO
Contact:

Re: Conversion from v12 to v20 problems

Post by Gavin Walker » Wed Jul 27, 2016 1:59 pm

No, you don't need to use the Conversion utility. Just restore the v17 back and it should auto-convert to v18.

caramel25
Posts: 12
Joined: Wed Jul 20, 2016 2:29 pm

Re: Conversion from v12 to v20 problems

Post by caramel25 » Wed Jul 27, 2016 2:13 pm

You mean, restore from the mbk file from v17?

User avatar
Gavin Walker
Posts: 4139
Joined: Wed Apr 04, 2007 10:11 pm
Location: Springfield, MO
Contact:

Re: Conversion from v12 to v20 problems

Post by Gavin Walker » Wed Jul 27, 2016 4:57 pm

Create a blank in practice in Medisoft v18 and then go to File -> Restore Backup and then browse and select the .MBK file you made from Medisoft 17 when you did the backup.

Post Reply