Thanks for trying to help.
Although your suggestion "CStr({Yourfieldname}" didn't work, your reply did get me thinkiing in another direction.
I went over to Business Objects and poked around until I came across a solution that made me wonder if my ohoice of OLE DB Provider could be the problem.
I was using "Microsoft OLE DB Provider for ODBC Drivers".
I created a new Q'n'D (quick n' dirty) report using "Microsoft OLE DB Provider for Oracle" and the errant Oracle Long field was able to be displayed in the report.
Now if I can just figure out a way to change the OLE DB Provider in my real report.
Any suggestions?
Again, thanks for the help.
-jrw