Kebabmeister
Programmer
We have just 'upgraded' to CR V9 (Yes I know) running on oracle 9 and one of the V8.5 reports now throws up this error. Copying the query and running it in toad does not throw up the same error so I imagine it is a CR query engine problem.
1) Has anyone ever run into this problem (You may have to think back a bit)?
2) Is there a patch we haven't got (product version 9.2.2.634)?
3) Anyone got any Paracetamol?
1) Has anyone ever run into this problem (You may have to think back a bit)?
2) Is there a patch we haven't got (product version 9.2.2.634)?
3) Anyone got any Paracetamol?