At first my end user use to print preview a report and use the export button to output the report as CSV. Because this is running on a server and the user is using remote desktop they kept getting an error because the export dialog box was trying to access the servers C drive which was not allow. Because of this I created my own export panel which had a dropdown of the person local drives (tsclient\c, etc). Then they would select from a dropdown the file type and press a Save button. The save button execute crxreport.export false command which works but it is taking 15 to 20 minutes to process this and the original method was almost instant. My question is why is the report export much slower than the viewer export?
Thanks for any reply,
Thanks for getting back to me. I'm not sure what you mean by 'which SDK' I am using. Basically it is a VB6 desktop (windows) application running throught Remote Desktop. The version is XI R2. I think I know what is happening. If I use the export button on the crystal viewer I think it is creating the data file locally or caching it in memory and then copying it to the client path. When I do the export in code not using the report viewer I think it is sending the data direct to the client.
I have tested this and the export button on the viewer is instant but the export in code takes a life time and I am only talking around 50 records.
Thanks again for your reply,
Moving to Legacy SDK forum.
Not enough info still but it appears to be a permission problem on the App server through RD.
Other issue is if you are allowing multiple users logging using RD then it could be a sharing issue. typically for this configuration one would use Citrix or terminal Server to share applications.
Try using ProcessMonitor to see what is happening on the Server.
Also, make sure you are using CR XI R2A Service Pack 4 and then SP 6 installed and runtime deployed.
Try adding logging in your app also to see where the delay is.
When you do use the Export Button in the viewer once the location is set I beleive it always goes to that new location specified. Another way would be to use a registry key to set the location also. ProcessMonitor will show you what it's doing.