Crystal Reports Viewer does not show up cross-tab object

[Former Member]

Hi everyone,

i have build a VB.NET CR Viewer Application in VisualStudio 2015. There in i select an existing report file to show up.

Within this report are some subreports and one of them with a cross-tab object.

On my development machine the reports works fine in SAP Crystal Reports as well as in my selfbuild CR Viewer Application.

On another machine, after i installed runtime and application the reports show up but not the cross-tab in the sub-report.

I tried to find a solution in the web, but did not find anything usefull.

I hope someone here can help me.

Whats wrong with my viewer app?

Any sugestions?

BG

Marcus M.

[former_member183750 · Accepted solution]

Hi Marcus

Probably the most efficient way to find out what is going on will be to download and install an eval of CR 2013 on that computer. Then see if you can run that report in the designer. It often gives you a better indication / error / behavior that will quickly lead you to a solution. I suspect this will be a data issue, but it may also be a design issue where the report may be suppressed if there is no data (I suppose a data issue again.).

Eval of CR 2013 is here:

SME Free Trials | SME Software | SAP

- Ludek

Senior Support Engineer AGS Product Support, Global Support Center Canada

Follow me on Twitter

[Former Member · Accepted solution]

Hi Ludek,

thanks for your remarks. It cant be a data issue. I do run the report on my development machine against the same data source with same parameters as on the normal pc with runtime installed.

Greetings

Marcus

[former_member11696 · Accepted solution]

Likely a dependency missing the crosstab object needs.

Run Process monitor on both and look for access denied or error...

Don

[former_member183750 · Accepted solution]

Sorry Marcus. Been there, heard that, over and over. Only one way to prove that this is not a data issue. Missing dependency is a possibility, but I'd still go for data issue. Easier to prove / disprove than slogging through 100s of lines in procmon logs.

- Ludek