QUESTION
 "Driver specified by data source name could not be loaded (4149)."
 received when connecting to database.

ANSWER
 This problem in VisualAge can happen when connecting to an
 Oracle or SQL Server or Sybase database.

 During installation, you should have been asked whether or not
 you wanted to initialize the odbc.ini file when you installed
 the VisualAge Sql Server or Oracle support.  If you did not
 answer 'yes', type and execute the following in your transcript
 for Sybase or SQL Server:
 AbtMultiDbSqlSvrDatabaseManager installIniFile

 or, for Oracle,

 AbtMultiDbOracleDatabaseManager installIniFile

 Other causes of this problem may be that the location of dlls
 starting with "qe" are not specified in the libpath in the
 config.sys (or path in the autoexec.bat on Windows).
 These qe*.dll files are supplied with VisualAge and reside in
 the -visualag-dll- directory on the client machine (standard
 VisualAge) or server (VisualAge Team).  For Sybase or SQL
 Server, the required file is qess04.dll and for Oracle,
 qe704.dll.  qelib.dll is also an important dll, required by
 both databases.

 Other potential causes of the problem using Oracle, are that
 the ORA7032.DLL file required by the VisualAge code is not
 present or its location is not specified in the libpath in the
 config.sys (or path in the autoexec.bat on Windows).  Oracle
 users must type a 'b:' before the server name on the connect
 if using SQL*Net for NetBIOS or 't:' for TCPIP.

 Other potential causes of the problem using Sybase or SQL Server
 are that the SYBDB.DLL file required by the VisualAge code is not
 present or its location is not specified in the libpath in the
 config.sys (or path in the autoexec.bat on Windows).

 For Sybase or SQL Server versions above 4.6 or for Sybase
 System 10, the user must install client code from Sybase
 that supports older versions of Sybase (has the sybdb.dll file,
 not the newer libsybdb.dll file).

 Also, users should remember that the server name must be
 typed in the correct case (lower or upper) that was used
 during installation.  In order to check this, the user
 may look at the sql.ini file in the SQL Server ini subdirectory.
 The ini file must be edited with a ini editor.  However, you
 can still see the server name by just typing the sql.ini file.