Crystal 10 is locking SQL tables - how to stop this.

[kapaa]

I really need help with this issue, I can't find much info anywhere that helps to solve this.

I recently upgraded from crw8 to crw10 and of course after converting reports and placing them into production I now discovered that crw10 will place locks (blocking) on the SQL tables it is using. I have read two posts about this: 766-1213672 and 7666-866882 and I tell you that something with Crystal is 'blocking' the tables it uses on our SQL db. I'm using a read-only account, have my ODBC setup to use this account, and when I run a report all looks okay in SQL until another application tries to use that table and then I see "blocking" in SQL.

Is there a setting in crystal so I can turn this off? Someone said to use a statement like ... "with (nolock)" but I can't seem to figure out the correct syntax to use. Then I saw something about SET TRANSACTION ISOLATION LEVEL READ UNCOMMITTED but when I tried this in my select statement Crystal spit it out. I desperately need help!!!

Example - if this is my select statement how would I add the "nolock" to it?

(DateTimeToDate (PDMTimeToDateTime ({call_req.open_date})) >= {?Starting Date}) AND
(DateTimeToDate (PDMTimeToDateTime ({call_req.open_date})) <= {?End Date}) AND
(if {?Select_Group} <> "ALL" then {ca_contact.last_name} = {?Select_Group}
else if {?Select_Group} = "ALL" then true) AND
{call_req.type} = {?Type}