For old DB versions, DB_UMODE may be changed to 0 and cannot be reset to 1 even after restarting in some situations, for example: OS reboot immediately without waiting DB Server terminated successfully.

To solve these problems, users need to alter the value of DB_UMODE to 1 by hand in dmconfig.ini. This issue has been resolved in versions built after 2010/5/20, and don’t need to reset by hand.

Version: DBMaker 4.3.x, 5.1.X, 5.2.X

Product: Normal/Bundle

Platform: Windows/Linux