CAUTION: This solution needs advanced Operating System knowledge. Consult your system administrator for help. Sage isn't liable for issues caused by improper changes to the Windows Registry. Always back up your data before applying advanced solutions.
CAUTION: Sage support can't assist with third-party products, hardware, report customizations, or state and federal tax questions. Refer to our Scope of Support for more info. Contact your Sage business partner, network administrator, or accountant for assistance.Note: This procedure may or may not work on any given operating system. Sage 100 Customer Support is not responsible for assisting or troubleshooting with this procedure, nor with setting up an external data connection for a third-party product to access Sage 100 data. Assistance by a qualified technician or consultant may be necessary.
Note: Steps are included in the Online Manual for Crystal Reports in Appendix C, under "Creating a Silent Connect DSN".
A new Data Source must be created. The existing SOTAMAS90 is reserved for Sage 100 ERP use and cannot be used to create a Silent Connection. Using SOTAMAS90 will result in the silent ODBC connection failing once Sage 100 ERP itself is started from the workstation. The user will be prompted for the Company code, User Code and Password the next time SOTAMAS90 is accessed from the external source.
Note: In some applications, User DSNs, such as SOTAMAS90_Silent will be displayed as a "Machine Data Source" since a User DSN is a machine specific concept.
Note: Be sure to disable (uncheck) the 'Dirty Read' and 'Burst Mode' checkboxes. An explanation of both options is below:
Dirty Read:
Default value = Enabled
If enabled, the driver attempts to use data already within its buffers from prior reads. In theory, an update could occur while the query is in progress and may be missed. In practice this is not likely to happen.
Burst mode:
Default value = Enabled
Note: Burst mode can be used when the execution of an SQL command and its associated 'data fetches' is going to be done without the application delaying for user input. The ODBC driver will apply short-term locks to improve performance between data fetch commands. When the application executes a SQL command then fetches a row, the physical data file will remain locked until at least 20 rows have been fetched (or EOF). This can be used with Report style access but should not be used for interactive access.