
Making software work for you
|
| View previous topic :: View next topic |
| Author |
Message |
| JamesJ
| | Joined: 17 Feb 2005 | | Posts: 133 | |
|
Posted: Tue Apr 10, 2007 5:17 pm Post subject: Does CC have to run the reports from temp copies? |
|
|
I took my first look at Crystal Corral today. We have quite a few reports here - Too many really - and something like this might help some users keep track of which reports they actually use and for what.
Some reports print the report path and name at the bottom of the page for one reason or another, but it's basically to help users identify a report, and find it when they want to run it. The reports use a built-in CR function/variable to output the report path and name.
The problem is that when I run a report from CC, instead of something like
S:/Crystal_Reports/<rest of path>/ Report_name.rpt
I get something like
C:/DOCUME~1/USERNA~1/LOCALS~1/Temp/ Report_name {FD1C02A2-DBC7-40E7-8CB9-1E6268C8C844}.rpt
(The forum is removing backwards slashes, so I substituted forward slashes in the paths)
Arguably, if someone is using CC to organize their reports, they may not need the report name as much, but it still may be needed at times, especially if someone else was looking at the printed report and wanted to run it. The basic name may be there (before that long hex string), but some of our report file names are fairly long and with that long path, there's a good chance that some names will get cut off by the field on the report. Also, while most of the "regular" reports are in the same directory, there are some reports in other directories and the original path is lost when running a report through CC.
So, does CC have to use a copy of the report, or can it run the original?
Or, more to the point, can CR's built-in report file name function/variable be made to show the original report path and name when a report is run through CC? It may not really matter where the report file that's being run is actually located, as long as the original path and name show on the report.
My guess is that this is just the way that the CR functions that you're using work and you have no control over it, but I figured I might as well ask.
Thanks.
James |
|
| Back to top |
|
 |
| kgroff Site Admin
 | | Joined: 27 Jan 2005 | | Posts: 694 | |
|
Posted: Wed Apr 11, 2007 6:26 am Post subject: |
|
|
James,
You guessed correct in that I don't have any control over the this and it sound like a bug within the support file included with VB.net.
-Kevin |
|
| Back to top |
|
 |
| JamesJ
| | Joined: 17 Feb 2005 | | Posts: 133 | |
|
Posted: Wed Apr 11, 2007 2:20 pm Post subject: |
|
|
I was afraid of that.
FWIW, I don't know if I'd call it a bug exactly. It appears that the VB.net routines are running the report from a copy of the RPT file, so the file name you get is the name of the copy. Seems like more of a design issue than a "bug".
Anyway, thanks for the response.
James |
|
| Back to top |
|
 |
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|