A family of Microsoft relational database management systems designed for ease of use.
Try a ntext field.
I think you have to use columns that support uni-code.
Now, keep in mind if I use ntext, then for the report wizard, yes, I do NOT see the formatted rich text as you state UNLESS I go into the report and set the particular text box as rich text.
So, after I open up the report in design mode, and set that particular text box as rich text, then it does work. Here is a screen shot.

I would let the wizard create a form on that same linked table, and then edit the rich text in the access form (access will display rich text edit control box). Or you could also test a cut/paste. Then try the report. (also, does a form show the rich text correctly? - test this since it might the the rich text format).
I would also take a quick look at the ntext field in sql studio and see how it looks. For me, I see for the above first row:
<div>Greater then 5000</div>
<div><font size=4><strong>This is bold</strong></font></div>
I am doing the above in a2010 with sql server 2005. I suspect this should work the same in access 2007.
So, try ntext. I guessing this might be a uni code.
Also, try the built in rich text editor that access displays when editing a form and the cursor moves into a rich text text box (it might be formatting, and this test will save you a big wild goose chase). So, try using access to enter some rich text to determine if this is an access formatting issue, or rich text format issue.
I suppose this is possible a 2007 issue. I do have access running in VPC somewhere, and if after trying the above you have no luck, then I will go to all the trouble to test this under access 2007, but I would try above first.
Note that I am using a standard linked table to sql server 2005, and I am NOT using a ADP (access data project).
--
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada
*** Email address is removed for privacy ***