Error getting Database property: Table: xxx, Subscript out of range - Dialog when Printing/Exporting

17 March 2007

Issue Description

We have seen this message: "Error getting Database property: Table: RM00102, Subscript out of range" When the Crystal Report is Designed using the new SQL 2005 native Client ODBC driver. (or possibly with an OLEDB driver instead of an ODBC driver)

 

 

Solution

The report should be designed using the classic "SQL Server Driver" ODBC driver, (use Set Datasource Location in Crystal to set the odbc DSN to one that was created with the classic SQL Server ODBC driver ) - once the report is designed, the Great Plains Application can use either type of ODBC driver, it is only at design time of the report that it causes the issue, (since the SQL 2005 native Client odbc driver does not use the same connection information entries that Forms Printer expects, and thus the Subscript out of range error occurs. )

You should use SQL Authentication (not integrated) and you should use the ODBC RDO connection type in Crystal Reports. (in the Create new connection folder, where you pick your created DSN)

Note that it is highly recommended to use a "Temporary" ODBC DSN name  when designing the report (one that will _Not_ exist on the workstations where Forms Printer eventually prints the report., See Appendix 1 of FPDOCXX.PDF in the Great plains folder for more info)

Let us know if you have further questions after Checking and trying the above.