显示标签为“assume”的博文。显示所有博文
显示标签为“assume”的博文。显示所有博文

2012年3月9日星期五

Fix

I assume you are using MSXML3 and Msxml2.XMLHTTP progid for posting your
updategrams.
Could you tell us what is the version of MSXML3?
Msxml3 version number is something like: 8.70.1113.0
Regards,
- Umut Alev
"AHilton" wrote:

> The error message stated was wrong, the correct one was:
> "The server returned an invalid or unrecognized response"
> We identified that posts from .net v2 were working and posts from classic
> ASP and client side javascript failed with the error above. We use XML v3 in
> javascript and classic ASP.
> By converting the XML to be posted to XML DOM v4 and posting using
> xmlHttp/serverXmlHttp v4, the problem went away. (At this point it's too
> difficult to convert the rest of the app to XML DOM v4)
> Andrew
Umut,
Yes, we were using MSXML3 via the progid 'Msxml2.XMLHTTP', which was changed
to ''Msxml2.XMLHTTP.4.0' in the fix.
The version number of MSXML3 that I have here is: 8.70.1113.0
Regards,
Andrew
"Umut Alev" wrote:
[vbcol=seagreen]
> I assume you are using MSXML3 and Msxml2.XMLHTTP progid for posting your
> updategrams.
> Could you tell us what is the version of MSXML3?
> Msxml3 version number is something like: 8.70.1113.0
> Regards,
> - Umut Alev
> "AHilton" wrote:

Fit dataset on one page

Hey guys,
Let's assume I have dataset with two columns (A,B) and it has 100 records.
I'd like to split this dataset on the same page with 25 records in every column. Side by side.

Example:

ColA ColB ColA ColB ColA ColB ColA ColB 25 rec 25 rec 25 rec 25 rec


What should I use and what properties I have to play with?
Thanks.anyone? :))|||Just a quick drop answer:

- I asume regular column format does not work for you because you want balanced columns and RS gives you unbalanced ones.
- I asume you have a static format= always 100 records, always 25 records/column, or alike.

In those circumstances:
- I'll put 4 table regions side by side on the report design area
- Create a sort of paging expression. Based on Chris Hays blog entry (http://blogs.msdn.com/chrishays/archive/2004/07/15/DynamicGrouping.aspx)
- But instead of grouping items, I'll use the expression for filtering contents on each table. So, table data region 1 will filter for those records with "group" value of 1, table 2 for group 2, and so on...

Hope this helps,

Jordi Rambla
SQL Server MVP (Reporting Services)
SolidQualityLearning|||A related query to you...

how do i control how many records are displayed on the page?. currently I do not see any property and RS just gives me some defaullt number of records on a page.

The problem is, in one case I get 3 records on a page and 2900 pages which I do not want.

Thanks.|||I'm guessing again, because I've not tried this in code, but I think you can follow the same dynamic grouping solution that Chris Hays suggest in their bloeg (see previous link) to have another grouping every 100 records and then adding a page break based on that grouping.

Let me sumarize the solution:

- One list region with grouping each 100 records (expression1) and page break after each group
- Inside the list: 4 table regions, each one holding 25 records filtered according to the block expression2 (now you may want take "page number" in account).

Hope this helps,

Jordi Rambla
SQL Server MVP (Reporting Services)
SolidQualityLearning|||Thanks Jordi,
However your assumption wasn't right enough. :)) Sorry.
In my situation recordset can be between 0 and 100 records.
I will try to manipulate with "region" tables.|||Hey,

I was still not able to control how many records are shown on a single page? Any ideas if there is a property I can configure to control this?

Thanks.|||Hi cvajre (whatever this means ;-)

No, there is no property to control how many reports are shown on a single page.
Keep in mind that RS is designed to support and handle rich free-form reports in an open number of presentation formats. That way, even the "page" concept is a tricky one.

You can set page breaks on groups (only?), therefore the trick mentioned above for creating groups that fit your expected recordnumber size.

Hope this helps,

Jordi Rambla
SQL Server MVP (Reporting Services)
SolidQualityLearning