# Unsupported Features Cross tabs, graphs, lines and boxes, and the SAM\_ReportNotify event are not supported. ## Cross tabs Cross tabs must be redesigned by hand because the implementation of cross tabs in Report Builder and Crystal Report are too different. ## Lines and Boxes Unfortunately we do not port lines and boxes because of a bug in Report Builder's COM interface. ## SAM\_ReportNotify The message *SAM\_ReportNotify* cannot be generated because CR.NET doesn't generate runtime events while formatting the report. Usually this can easily be replaced by one of the supported *SAM\_Report*\* messages, typically *SAM\_ReportStart*. *SAM\_ReportNotify* is not supported because the version of Crystal Reports that ships with Visual Studio doesn't generate formatting notifications. In most cases, the code in *SAM\_ReportNotify* can be moved in the other SAM\_Report messages. ## Null values Crystal Report doesn't support passing null values to functions, more accurately, CR treats null values as a database engine would and nulls the entire expression. In case the report logic contains a formula that expects a null value, after porting the result of the formula evaluation will always be null. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.iceteagroup.com/general/ported-reports/crystal-reports/unsupported-features.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.