BigLouie over 6 years ago. Contact your system administrator for assistance. Besides this, I find the message regarding ODBC connections failing IF the registry entries are removed somewhat misleading, since these fail even if one selects “No” at that prompt. Now, this was bit Windows 7, and I know there would be some adjustments for bit Windows 7 and even perhaps for XP, but those can wait. Sage is not responsible for operation issues caused by incorrectly modifying your Windows Registry. Select the first remote user and click the Preferences tab. If the Windows Explorer window opens unchallenged, but appears slowly, the remote workstation may be experiencing a slow name resolution issue.
|Date Added:||19 October 2005|
|File Size:||16.79 Mb|
|Operating Systems:||Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X|
|Price:||Free* [*Free Regsitration Required]|
For Sage Advanced versions and highersee the Related Resources section in this document. Ofbc enable for an individual user after setting up in System Configuration: Description — Enter a meaningful description.
how to install SOTAMAS90 odbc driver – MAS 90 (Sage) solutions – Tek-Tips
The requirement is that from the workstation, entering the UNC path to the. Repeat above steps for every remote user. Maybe it is a faulty assumption on my part that there would be a conflict indtall I hoa to install 4. If the Create Shortcut window opens, click Cancel. In the end, the solution was simple: If Deferred is selected, the user can then print from Deferred to the printer. Correct this problem before proceeding to the next step.
Install ODBC driver without workstation setup
Preview the company listing report again. Expand Library Master and Reports. These are not required, however.
When printing a form or report from a Legacy module, all the odnc user’s printers will appear. This DLL behaved slightly differently from the other one in that, while it remained in place in System32 until reboot, it disappeared upon reboot. This solution requires advanced knowledge of your computer’s operating system.
ODBC Drivers for MAS 90 and MAS
Contact your system administrator for assistance. If you do not receive and ISAM error, and the report appears after renaming the registry key, the standard driver was being used.
Additional Notes Reports and Forms run slower the first time. The first time a Crystal form or report is printed from the remote workstation using the CS ODBC driver, it takes longer to print because the report is cached locally under the following folder: This option is available in Sage MAS 4. Adding it back to the registry gave me what I think is a fully-functional DSN without a prior workstation installation on the computer.
All is good now, though I think. Click the Test Connection button.
The setup routines for the MAS90 4. Remote users must have sufficient Windows permissions on their local computer for Sage MAS to copy the. If an ISAM error occurs, review all previous settings, paying close attention to step 1.
I could have saved some time hiw just looking to see if it stayed there in the first place, but either way, it was to no avail, as I received the same message as above: Configure the corporate firewall and router policies to allow port to be accessible from the remote workstations. Rename the following key: Modifying Windows security incorrectly can severely affect system operations.
The service can run on the system account; there is no reason to change the log in. The next step was to see if it just needed to be re-registered, so I ran msa90 Database Directory — This is important.
Verify that personal firewall software on the workstation and the server’s firewall or router is configured correctly.