of the Msdadc.dll file installed by Setup and
the existing version of the Ole32.dll file on
the target computer.To resolve this
problem, install Internet Explorer 4.0 or later.
For more information, refer to article Q194197 from Microsoft Technet or the Microsoft
Knowledge Base on the internet at http://www.microsoft.com. Click Support
Tab…Knowledge Base.
"ODBC Resource DLL Is a Different Version
Than ..."
During the installation of ODBC, a service or application was
using one or more ODBC files. The files that were in use could not be overwritten, causing
a version mismatch between the files that were in use and either the ODBC Driver Manager
or the ODBC Administrator.
To resolve this problem:
- Close all Programs
- Remove the current TTG Back Office Product Suite by clicking
Start…Settings…Control Panel
- Double-click the Add/Remove Programs icon
- Select TTG Back Office Product Suite
- Click Add/Remove
- Click Remove All
- Click Yes
- Click Restart Windows
- Hold down the SHIFT key while it is restarting (Doing this
will start Windows 95 in safe mode, and will bypass most applications that load at
startup)
- Run Setup again
For more information, refer to article Q170769 from Microsoft
Technet or the Microsoft Knowledge Base on the internet at http://www.microsoft.com. Click
Support Tab…Knowledge Base.
"Connection Failed" or "Connection
Handle Invalid"
Verify that AfW can connect from this PC. This will confirm
that the network is setup properly on the workstation. If AfW can connect, one of the
options is usually incorrect in the setup window.
To resolve this problem:
- Server should appear exactly as it does in AfW Help…About
Window (Do not use slashes or any kind of path)
- UserID should be sa
- Password should be the same as the DBO password in AfW
If these are all correct, then:
- Click Start…Settings…Control Panel
- Double-Click the ODBC32 icon
- Find the DSN with the name specified in the TTG Back Office
Product Suite® setup. (Default is agenasql)
- Click Configure
- Name and Description should be the same as Name in the Setup
- Server should be the same as AfW's Help…About window
- Click Next
- SQL Server Authentication should be checked
- LoginID should be sa
- The password is not entered by design of Microsoft ODBC
- Type in the password of your AfW DBO user
- Click Next
If you get an error at this point, one of the settings
discussed above was not done correctly.
- Check your spelling
- If you get to the next screen, Check Change the Default
Database to Verify that the database selected is the same as in AfW's Help…About (The
default is AFW1)
- Leave all the other settings alone
- Click next until you get the finish button
- Click finish
If you do not get any errors in the ODBC32 settings, your
connection should be working. If server, name, userid, or password were changed in ODBC32
they need to be changed in the setup window also.
Please Contact Us for
more information.
|
