Thank you for your quick respond. I don’t get what you mean by upgrading the database. I created backup using the built-in create backup under Administration. I then uploaded that into a new version of OpenEMR (4.2.2). Beside that I didn’t know what else I have to upgrade.
Also, the link you provided, all I have to do is just copy the codes into the correct files?
No, don’t change any code. Sounds like you need to browse to openemr/admin.php in your openemr site and see if there’s an “upgrade database” link. If yes you need to run that.
Do admin.php again and see if it’s still asking you to do the database upgrade. If so, the upgrade must have failed.
When you run the database upgrade it dumps a bunch of messages to the screen, showing what it did. You should scroll through all that to see if there were any errors in red. If there are any, report back with details.
I updated by going to localhost/openemr/admin.php yesterday and I don’t remember it having anything red. But right now it still have the same problem. Right now when I go back into the Lists under Administration - for all the Lists I tried that gave me error before, all the information were gone. So do I have to manually add each on back individually? Thanks
Not enough information. Does admin.php still have an “upgrade database” link? If so, did you run it again? Also exactly what information is gone? For that, try posting a screenshot.
OK so it appears that in spite of the upgrade being done, the subtype column is still missing. You’ll have to fix this first. Instead of admin.php, go to sql_upgrade.php. Be sure to select from the dropdown the release that you are upgrading from. Then do the upgrade and when it’s done scroll through the output as already mentioned. Somewhere in there you should see:
ALTER TABLE `list_options` ADD COLUMN `subtype` varchar(31) NOT NULL DEFAULT ''
Assuming that happens, your error message should be fixed. Then yes, you will need to add back the data for any lists that got zapped by this.
You have to upgrade from release 4.2.1 or earlier to get this and probably other required fixes. Sounds like you selected 4.2.2 and so the required changes were not done. What release were you on before? Whatever it was, select that one.