disabling massive report

[Peter DeGroot]

I'm having trouble with a seemingly massive report that reports only four dimensions.

I have opened a relatively small 3.7mr2 program with 4.1. When I run it, the report is over 200 pages long. In 3.7 the report is one page.

It has the header, 200 or so blank pages and then the four dimensions are on the last page.
I have done this with other similar programs without a problem, but this one keeps opening this massive report.

Any suggestions?

Thanks in advance.

[JamesMannes]

I do believe this is the "fix" for a lot of issues, so if it sounds repetitve, forgive me, so if it sounds repetitive, forgive me. Close out PC-DMIS. Go into your Program Files>>WAI>>4.1>>(your screen name), look for the executebarstate, delete it. Shutdown, restart, run your program, while the program is running, ensure that (while the program is running) you have the probe Readout window open, of course your Execution Mode Options window will be open, and your Report window also needs to be open (you can minimize it thats ok).

[John Kingston]

James,
You are being repetivitely redundant.
But you you are are right right about about the the fix fix.
John

[craiger_ny]

WTF is that? That sounds like some unknown cheat code for endless health in World of Warcraft or something. How does that manage to fix it and how the heck did you discover that? That is just freaking bizzare.

Craig

[JamesMannes]

Hey....

I AM IRON MAN!!!

[JamesMannes]

Actually my PDF's weren't writing properly so I called, get ready, Tech Support, and they were able to help me. That was their remedy for the PDF stuf so I have since kinda been using that for a few fixes. As an example if the executebarstate is corrupted (see, keep you report window open), if you have a print command in the program, it sometimes will not print due to this corruption.

[Peter DeGroot]

Thanks - NEVER would have found that. Worked perfect
.....I went to the user group meeting too. also went to 4.0 training two weeks ago @ elgin. After that the usergroup was pretty redundant as well. ...donuts were pretty good

[cmmguy]

Actually my PDF's weren't writing properly so I called, get ready, Tech Support, and they were able to help me. That was their remedy for the PDF stuf so I have since kinda been using that for a few fixes. As an example if the executebarstate is corrupted (see, keep you report window open), if you have a print command in the program, it sometimes will not print due to this corruption.

They didnt tell you to stand on one foot while doing the above by any chance...