i need some help! i created a custom report in MAS through report manager. I used crystal report as tool, since it is bundled with MAS200. After testing the report, running it in crystal report and found that it works fine, i added it to menu. We were using crystal reports for web since our server is far from the workstations. But when i run the report from a workstation, it prompted for username and password. after i enter the info, it prompted me again and again. i dont know what to do with this. please help!!!! thank you in advance..
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
i need some help! i created a custo
- Thread starter jocs
- Start date
Omnicef
MIS
- Feb 10, 2003
- 78
You need to create a silent odbc connection and configure the report to use it instead. This is how you create a silent connection:
To create a silent connect ODBC data source; follow the steps below. The existing SOTAMAS90 data source cannot be used. This is reserved for MAS90. A new Data Source must be created. Attempting to use SOTAMAS90 will result in the silent ODBC connection failing once MAS 90 itself is started from the workstation. The user will be prompted for the company code, user code and password.
1. In Windows, select Start, Settings, and Control Panel.
2. Double-click the 32bit ODBC icon. On some systems, this icon appears as "ODBC Data Sources (32 bit)."
3. Choose the Add button under the User DSN tab. The Create New Data Source window appears.
4. Select MAS 90 32-Bit ODBC Driver and choose the Finish button. The ProvideX 32-bit ODBC Setup dialog box appears.
5. Enter a new data source name (DSN). For example, you could create SOTAMAS90_silent. Do not use spaces or blanks in the data source name.
Note: Versions prior to 3.40 MAS90 require the DSN starts with the letters SOTA
6. Enter a description for the data source.
7. Enter the database directory location; this is the path to the MAS90 directory (for example, C:\MAS90). If you are using MAS 90 Client/Server, this is usually the UNC path to the MAS90 directory. This is the same path found under the SOTAMAS90 Data Source.
8. Leave the Definition File field blank.
9. In the Optional Information section, enter a valid 3-digit MAS 90 company code. Be sure to enter this in UPPER case letters. Entering the company code in lower case will cause the silent ODBC connection to fail.
10. Enter the default user ID. This is your MAS 90 user code. Be sure to enter this in UPPER case letters. Note that 2 digit user codes will cause the silent odbc connection to fail. You must enter it as 2 digits followed by a space. For example, instead of using "AC" use "AC "
11 Enter your MAS90 password. Do not use spaces or blanks in the password name, as this will cause the silent ODBC connection to fail. If the MAS90 password contains spaces, it must be changed in MAS90 User Maintenance.
12. Choose the OK button.
13. Exit the ODBC Data Source Administrator and Control Panel
14. Use the 3rd party application to connect to the SOTAMAS90_Silent data source. Do not connect to the SOTAMAS90 data source. The 'MAS90 Database Signon' dialog box should not appear if the logon credentials were entered correctly for the SOTAMAS90_Silent data 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.
On MAS90 versions 3.41 and higher a new version of ProvideX ODBC Driver that has new performance related options that are enabled by default but must be disabled for access outside of the Crystal Reports environment. These options are Dirty Read and Burst Mode, which must be unchecked. An explanation of both options is below:
Dirty Read mode:
Default value = Enabled
If enabled, the driver attempts to use data already within its buffers from prior reads. In theory you could thus have an update occur while the query is in progress that may go missed. In practice this is not likely to happen.
Burst mode:
Default value = Enabled
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.
I hope this helps!
Thnks in advance to all users out there who continually answer all of our questions. Although I try to answer some questions, I usually am asking.
To create a silent connect ODBC data source; follow the steps below. The existing SOTAMAS90 data source cannot be used. This is reserved for MAS90. A new Data Source must be created. Attempting to use SOTAMAS90 will result in the silent ODBC connection failing once MAS 90 itself is started from the workstation. The user will be prompted for the company code, user code and password.
1. In Windows, select Start, Settings, and Control Panel.
2. Double-click the 32bit ODBC icon. On some systems, this icon appears as "ODBC Data Sources (32 bit)."
3. Choose the Add button under the User DSN tab. The Create New Data Source window appears.
4. Select MAS 90 32-Bit ODBC Driver and choose the Finish button. The ProvideX 32-bit ODBC Setup dialog box appears.
5. Enter a new data source name (DSN). For example, you could create SOTAMAS90_silent. Do not use spaces or blanks in the data source name.
Note: Versions prior to 3.40 MAS90 require the DSN starts with the letters SOTA
6. Enter a description for the data source.
7. Enter the database directory location; this is the path to the MAS90 directory (for example, C:\MAS90). If you are using MAS 90 Client/Server, this is usually the UNC path to the MAS90 directory. This is the same path found under the SOTAMAS90 Data Source.
8. Leave the Definition File field blank.
9. In the Optional Information section, enter a valid 3-digit MAS 90 company code. Be sure to enter this in UPPER case letters. Entering the company code in lower case will cause the silent ODBC connection to fail.
10. Enter the default user ID. This is your MAS 90 user code. Be sure to enter this in UPPER case letters. Note that 2 digit user codes will cause the silent odbc connection to fail. You must enter it as 2 digits followed by a space. For example, instead of using "AC" use "AC "
11 Enter your MAS90 password. Do not use spaces or blanks in the password name, as this will cause the silent ODBC connection to fail. If the MAS90 password contains spaces, it must be changed in MAS90 User Maintenance.
12. Choose the OK button.
13. Exit the ODBC Data Source Administrator and Control Panel
14. Use the 3rd party application to connect to the SOTAMAS90_Silent data source. Do not connect to the SOTAMAS90 data source. The 'MAS90 Database Signon' dialog box should not appear if the logon credentials were entered correctly for the SOTAMAS90_Silent data 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.
On MAS90 versions 3.41 and higher a new version of ProvideX ODBC Driver that has new performance related options that are enabled by default but must be disabled for access outside of the Crystal Reports environment. These options are Dirty Read and Burst Mode, which must be unchecked. An explanation of both options is below:
Dirty Read mode:
Default value = Enabled
If enabled, the driver attempts to use data already within its buffers from prior reads. In theory you could thus have an update occur while the query is in progress that may go missed. In practice this is not likely to happen.
Burst mode:
Default value = Enabled
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.
I hope this helps!
Thnks in advance to all users out there who continually answer all of our questions. Although I try to answer some questions, I usually am asking.
- Status
Similar threads
- Locked
- Question
- Locked
- Question