To All,
Thanks to Mike at RBTI for working with me on this problem and together we
came up with the solution. Mike noticed that under the create breakpoint
dialog I had the Keep Next Section and Keep Previous Section both checked
off. We decided to uncheck these and the report worked with the column as
the breakpoint.
The moral of the story is leave both of those values unchecked.
Jeff
>To All,
>
>I seem to be the king of strange bugs. Here's another one.
>
>I wrote simple report in the latest version of RBWin based on a
>view. There was one break point in the report on CustomerID. When I
>added an F1 section to the report and ran it I would get a GPF and thrown
>out of RBase every time even if I just printed it from the R:Prompt.
>
>So I decided to move the report to a single table and use lookups. Same
>problem. But again, if I removed the F1 section the report worked every time.
>
>I tried it on my customers machine and same problem.
>
>Mike at RBTI was very helpful and I unloaded and recreated the database,
>uninstalled and reinstalled RBWin and the patch. made sure my .INI file
>was correct and the problem persisted. The version of the report without
>the F1 section always worked.
>
>For some strange reason I decided to create a variable 'rvcustomerid =
>customerid' and I made the variable rvcustomerid the breakpoint instead of
>the column and the report worked every time!
>
>Also, this customer likes to view reports to the screen, but I have found
>that if I use the Enter key to move the report down instead of the PgDn
>key I lose my mouse function and have to reboot.
>
>Has anyone experience any problems like these?
>
> Jeff
>
