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 bkrike on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Crystal Error in MAS90 3.51 Purchase Order printing
- Thread starter jfeltch
- Start date
It is my guess that you just recently found an old copy of MAS v3.51 and installed it. Would this be correct?
"Error detected by database.DLL", when printing or previewing Crystal reports
Entry Type: Informational
Product: Sage MAS 90 ERP, Sage MAS 200 ERP, Sage MAS 200 ERP - SQL Server Edition
Application: Crystal Reports
Version Reported: 3.61
Subject:
"Error detected by database.DLL", when printing or previewing reports using Crystal Reports. Error "ODBC error: [PROVIDEX] [PVX ODBC DRIVER] [FILEIO] Physical file is not accessible. On version 3.71 may get "Crystal database is in use by another user"
Note: "PESTARTPRINTJOB" also appeared on the error screens in older Sage MAS 90 versions, but should no longer appear on newer versions.
Possible Resolutions:
Note: "Error detected by database.DLL" is a very generic error.
For a more specific error, click on the 'Design' or 'Form' button and refreshing the form or report from within Crystal Reports (click on the Lightning Bolt button). Search the Knowledgebase for the specific error.
The error might occur for the following reasons:
The user has been denied access to the files with ODBC Table/File security or ODBC User Security.
The report is pulling data files that do not exist for the Company Code.
The UNC path may be incorrect in Alternate Directory Maintenance (Sage MAS 200).
The form or report may have been created in a prior version and needs to be converted to the current version.
The P2SODBC.DLL file may be the incorrect version
There are two or more left outer joins. The SOTAMAS90 dsn only supports a single left outer join.
A report run from the Custom Reports menu is accessing a table or file outside Sage MAS 90 or 200. The report can only be run outside of Sage MAS 90 or 200.
"Error detected by database.DLL", when printing or previewing Crystal reports
Entry Type: Informational
Product: Sage MAS 90 ERP, Sage MAS 200 ERP, Sage MAS 200 ERP - SQL Server Edition
Application: Crystal Reports
Version Reported: 3.61
Subject:
"Error detected by database.DLL", when printing or previewing reports using Crystal Reports. Error "ODBC error: [PROVIDEX] [PVX ODBC DRIVER] [FILEIO] Physical file is not accessible. On version 3.71 may get "Crystal database is in use by another user"
Note: "PESTARTPRINTJOB" also appeared on the error screens in older Sage MAS 90 versions, but should no longer appear on newer versions.
Possible Resolutions:
Note: "Error detected by database.DLL" is a very generic error.
For a more specific error, click on the 'Design' or 'Form' button and refreshing the form or report from within Crystal Reports (click on the Lightning Bolt button). Search the Knowledgebase for the specific error.
The error might occur for the following reasons:
The user has been denied access to the files with ODBC Table/File security or ODBC User Security.
The report is pulling data files that do not exist for the Company Code.
The UNC path may be incorrect in Alternate Directory Maintenance (Sage MAS 200).
The form or report may have been created in a prior version and needs to be converted to the current version.
The P2SODBC.DLL file may be the incorrect version
There are two or more left outer joins. The SOTAMAS90 dsn only supports a single left outer join.
A report run from the Custom Reports menu is accessing a table or file outside Sage MAS 90 or 200. The report can only be run outside of Sage MAS 90 or 200.
- Thread starter
- #3
- Status
Similar threads
- Locked
- Question