If anyone has found this thread through the search facility this is for your benefit.
For about a week I was kicked out of Crystal with this error message whenever I tried to place a field on the report. It was driving me mad but I've found out why it was happening. I know there are a number of reasons why this happens, but this is worth checking out first.
I have 2 monitors connected at the same time - my laptop monitor and a large, separate monitor to my left which is my secondary monitor. The error only occurred when I used Crystal on the secondary monitor.
I moved the secondary monitor to my right and set the display properties accordingly (so the cursor must move to the right to get onto the secondary monitor) and the issue disappeared!
Apparently this is because when a secondary monitor is to the left, the screen co-ordinates are negative, and this must somehow confuse Crystal when a new field is placed on the report. Moving the monitor to the right makes the screen co-ordinates on the secondary monitor positive and therefore fixes the issue.
Hope that helps someone,
Tim.
For about a week I was kicked out of Crystal with this error message whenever I tried to place a field on the report. It was driving me mad but I've found out why it was happening. I know there are a number of reasons why this happens, but this is worth checking out first.
I have 2 monitors connected at the same time - my laptop monitor and a large, separate monitor to my left which is my secondary monitor. The error only occurred when I used Crystal on the secondary monitor.
I moved the secondary monitor to my right and set the display properties accordingly (so the cursor must move to the right to get onto the secondary monitor) and the issue disappeared!
Apparently this is because when a secondary monitor is to the left, the screen co-ordinates are negative, and this must somehow confuse Crystal when a new field is placed on the report. Moving the monitor to the right makes the screen co-ordinates on the secondary monitor positive and therefore fixes the issue.
Hope that helps someone,
Tim.