We have tried reinstalling and we get the same problem. It also seems strange that this is ocurring on two different machines. Thoughts of ours have been:
Windows 2000 issue
VB service pack 5 issue
IAS issue
Unfortunately, we're still stuck
Yes, the subreports were definately edited by way of "edit subreport..." not by editing the originals. It seems we don't have this problem if we edit from within the VBdesigner rather than from within the Crystal Reports Design App.
I'm trying to run a report in an ASP page. The report has charts. Whenever the page loads, I get an error - "Invalid TLV record".
According to Seagate's knowledge base, the problem is a missing dll - pg32conv.dll to be exact. Unfortunately, when I try to register this .dll, the...
Thanks for your prompt response. I'm using version 8, although some of the subreports were originally created with version 7. Is there no other work around than reimporting the subreports? I have a large number of subreports on my main report( about 20 ), each of which has a corresponding hidden...
I'm using the Crystal Reports design viewer inside a VBApp.
A very strange thing thing is happening, older versions of the subreports are being displayed. When I run the report from within Crystal Reports, the most recent subreports are used. If I then import that same .rpt into a new VBApp, I...
I'm using Crystal Reports Version 7 and am having a problem suppressing subreports.
The first 3 I suppress using the " extra subreport/fetch shared variable/conditionally suppress section " method works fine. However if try to suppress more than the formulas retrieving the shared...
Yes, I have selected 'can grow' for each of the original subreports, and deselected it for each of the duplicate subreports used for suppression. I've tried it with 'can grow' selected for the duplicate subreports but this didn't affect anything.
I'm developing a report that has numerous subreports, 4 in the group header and 4 in the details section. I'm suppressing these reports when they are blank by using seagate's suggested approach... insert a duplicate subreport in a section above the original subreport, pass the isNull check for...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.