Linda,

>I'm having trouble with people not being able to run reports or queries because of a record lock. When I tracked down the problem, it appears that MM is adding code to my stored procedures SET NO_BROWSETABLE ON before the query. That is causing reports and queries to hang up until the user saves or cancels changes. Do I need to have different procedures to pull data for viewing/reporting than I do for updating? If so, what do I need to do differently?

It looks like this code is only inserted when calling GetEmptyDataSetBySproc(). Is that the method that's being called in this case?

Best Regards,