If I view a report via a browser using seagate's 8.5 ASP code, and that report is built using stored procedures, it will hang when you attempt to export the result to any formats. If I change the report to use tables, then the exports will work successfully. Does anyone know, are there any limitations to exporting reports viewed in a browser that were built using stored procedures? Anyone else successfully exporting reports using this combination of deployment? Exporting from the crystal designer doesn't have any problems with the stored procedure built reports.