I often see some people asking such problems in the forum. The problem that causes the ASA database that cannot be connected: 1, ODBC configuration error. There is no configuration of the data source, the username or password error, etc., will cause the database to be unable to connect. Solved approach: Check the configuration of the data source, if the data source is not configured in the ODBC, add the data source according to the wizard; password error only needs to be changed. 2, prompt the log file error when connecting. Most of this problem occurs after reinstalling the system, the source code is transplanted to other systems, and the database file path changes. Solved approach: Do not create a log file when you create an ASA database, and if you have created a log file, you can use the PB's own tool Sybase Central to remove the association of the log file and database file. The operation steps are as follows: a) Start Sybase Central Select Utilities; b) Double-click the Change Log File Settings in the entry on the right, directly next; c) Point Browse Select the database file that needs to remove the log file, select Behxt; d) Here you will see some database information, log file name, file size, etc. Next; E) Remove the pair of MAINTIN The Following Transaction Log File, Finish; f) configures the ODBC connection database. 3, the database file is corrupted. Such errors are generally uncommon, possibly due to virus damage or misuse operation. Solved approach: If you have previously backed up the backup file, you can only re-establish the library if there is no backup file!
