C# Developers' Journal (original) (raw)

11:53a

Old-school databinding and DataMembers Yes, I'm back.

( codeCollapse )

This code generates an error. After two hours of looking around the web, I finally got pointed to this KB article, which tells me my problem stems from the fact that my DataMember has a period in it, and that this bug is considered a "feature" by Microsoft. As you can see, I have tried setting the datasource directly to the relation; this results in the form loading and the datagrid remaining empty no matter what I do.

I need to find a way to set the datasource of the datagrid to the relation in question. It seems to me that the easiest way to do this will be to set the view dsViewHospitals to only show the relation in the dataset, but I'm not finding any code samples for how to set view to anything other than DefaultViewManager programmatically at Microsoft. How would I go about doing such a thing? Thanks.

9:37p

Query Analyzer Vs. SRS... different results So, I'm posting here in hopes that someone has encountered something like this before and knows a way to fix it.

this is a larger issue, but the crux of it is simply this query (yes it calles a sql server stored proc):

spRPT_TKT_ThreeDayCountReport null,null,null,null,null,null,'9/16/2006','10/15/2006',null,null,null,null,null,null,null,null,null

When executed from query analyzer (paste in, hit f5) connected to the production database I get one set of results.
When executed as a dataset (command type: text) in Sql Reporting Services, I get a different set of results.

The row counts and MOST of the associated data are exactly the same, the problem lies in SOME of the individual items are 0 (not null, just 0), in all cases these are sum(isnull(-variable-),0) items in the Sproc.

I am at a loss for why the results to this query are different from one application to the other. (and they are 100% reproducable).

any ideas?