Difference between revisions of "ITrack/IDispatch error 31826"
From ISoft Wiki
< ITrack
Jump to navigationJump to search
Daytonlowell (talk | contribs) (made the solution section even clearer) |
Daytonlowell (talk | contribs) |
||
| Line 9: | Line 9: | ||
Possible reasons the query would fail: | Possible reasons the query would fail: | ||
* Something wrong with the report you are trying to print. | * Something wrong with the report you are trying to print. | ||
** Report isn't up-to-date | ** Report isn't up-to-date | ||
** User's database is not up to date | ** User's database is not up to date | ||
** Correct parameters were not passed in to the report. | ** Correct parameters were not passed in to the report. | ||
* The ODBC driver is pointed at the wrong server. | |||
* The wrong report may be referenced in Edit > Options > Reports tab, causing ITrack to think that incorrect parameters are being passed in. | * The wrong report may be referenced in Edit > Options > Reports tab, causing ITrack to think that incorrect parameters are being passed in. | ||
Revision as of 15:20, 5 April 2011
"Failed to retrieve data from the database."
Cause
This error occurs when Crystal was able to connect to a MySQL database, but the report query returned with an error.
Solution
Possible reasons the query would fail:
- Something wrong with the report you are trying to print.
- Report isn't up-to-date
- User's database is not up to date
- Correct parameters were not passed in to the report.
- The ODBC driver is pointed at the wrong server.
- The wrong report may be referenced in Edit > Options > Reports tab, causing ITrack to think that incorrect parameters are being passed in.
