Monday, March 19, 2012
bug: "autostat" of an index reported by SQL Server Management Studio for 2005
SQL server management studio does not seem to display the "autostat" of
an index correctly. The value in SQL server management studio is
always the reverse of the value from "sp_autostats".
to reproduce, high light a table in object explorer -> right click to
select Modify -> click "manage indexes and keys" -> select the index ,
the value of "Re-compute Statistics" is always the reverse of the value
of the corresponding index from "sp_autostats".
Thanks.
Kong
(likong@.email.com) writes:
> Do not know if any one has complained this to Microsoft.
> SQL server management studio does not seem to display the "autostat" of
> an index correctly. The value in SQL server management studio is
> always the reverse of the value from "sp_autostats".
> to reproduce, high light a table in object explorer -> right click to
> select Modify -> click "manage indexes and keys" -> select the index ,
> the value of "Re-compute Statistics" is always the reverse of the value
> of the corresponding index from "sp_autostats".
Actually, I can't recall having seen this particular issue reported.
When playing around, it appears that someone has gotten confused over
the DLL, where the option is STATISTICS_NORECOMPUTE=ON/OFF. If you believe
what the dialog says, and change No to Yes, you will alter the setting.
The place to report bugs like this is
http://lab.msdn.microsoft.com/ProductFeedback/, and I encourage you to
go there.
By the way, if you right-click the index, select Properties, and go to
the Options page, you will see that on this screen they have it right.
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pro...ads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinf...ons/books.mspx
Bug MissingMethodException in application
Hello!
I wrote an application which runs correctly on my iPaq HP 5500 series. I used VB .Net 2003 to write it. I bougth a new Pocket PC iPaq HP hx 2790b. I deployed this application on my new Pocket PC. I get an exception when the application tries to execute this instruction "LEng = New SqlCeEngine("Data Source= " & AccessBase).". The exception is "MissingMethodException". I don't know what to do?
All the best,
Yang
Hello!
I wrote an application which runs correctly on my iPaq HP 5500 series. I used VB .Net 2003 to write it. I bougth a new Pocket PC iPaq HP hx 2790b. I deployed this application on my new Pocket PC. I get an exception when the application tries to execute this instruction "LEng = New SqlCeEngine("Data Source= " & AccessBase).". The exception is "MissingMethodException". I don't know what to do?
All the best,
Yang
|||Hi Yang,
First of all your connection string does not look ok. Secondly can you check that SQL Compact is actually getting deployed to you PPC when you deploy the application? Also let me know which verison of SQL Compact are you using?
Manish Agnihotri
Program Manager
SQL Compact
|||Just a few questions:
- Have you installed the same version of SQLCE?
- Which .NET Compact Framework are you using?
ow, and google is your friend :
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=679548&SiteID=1
Greetings from the rainy Netherlands
Thursday, March 8, 2012
Bug in Report Server?
I am running a report using RS2005. It connects to a web service using the XML data source. It works correctly in my development environment. When I put it up on the server and run the report, I get the error message:
If I run the web service from the server, it returns correct data, so I know error is not coming from my web service. The only answer I can think of is that there is a bug in the Report Server's or XML Data Source's code.
Has anyone else seen this problem?
Thank you,
Jessica
Hi Jessica, could you please repro the bug and send me most recent RS logs to almineev. At microsoft. Com.
RS logs are located at location similar to this one: C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\LogFiles
|||Jessica, did you ever find out the solution for your problem? I am experiencing a similar issue now.
Thanks,
James
|||It hapened to me, more or less the same.For what I know it can be a problem with the default values of the
Report Parameters... they should not be originated by a query.
I had this problem and puting this as static or calculated values solved the issue...
Not the best way as by default the user's are not getting the data shown, but that's a solution.
Hope Microsoft solves the issue.. as this is a serious bug.
Regards,
Jose|||
Our problem was two report items on top of each other. Once we moved one of them over by just a little bit, the error went away.
I'm assuming it was something in the server code that wasn't handling the scenario of the same positional coordinates being inserted into a hash table, but that's just a guess.
We solved it by recreating the report one item at a time, uploading after each item. When we layered the second item on top of the first, that's when we received that message.
Good luck with everyone else trying to get this to work!
-Jessica
Bug in Report Server?
I am running a report using RS2005. It connects to a web service using the XML data source. It works correctly in my development environment. When I put it up on the server and run the report, I get the error message:
If I run the web service from the server, it returns correct data, so I know error is not coming from my web service. The only answer I can think of is that there is a bug in the Report Server's or XML Data Source's code.
Has anyone else seen this problem?
Thank you,
Jessica
Hi Jessica, could you please repro the bug and send me most recent RS logs to almineev. At microsoft. Com.
RS logs are located at location similar to this one: C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\LogFiles
|||Jessica, did you ever find out the solution for your problem? I am experiencing a similar issue now.
Thanks,
James
|||It hapened to me, more or less the same.For what I know it can be a problem with the default values of the
Report Parameters... they should not be originated by a query.
I had this problem and puting this as static or calculated values solved the issue...
Not the best way as by default the user's are not getting the data shown, but that's a solution.
Hope Microsoft solves the issue.. as this is a serious bug.
Regards,
Jose|||
Our problem was two report items on top of each other. Once we moved one of them over by just a little bit, the error went away.
I'm assuming it was something in the server code that wasn't handling the scenario of the same positional coordinates being inserted into a hash table, but that's just a guess.
We solved it by recreating the report one item at a time, uploading after each item. When we layered the second item on top of the first, that's when we received that message.
Good luck with everyone else trying to get this to work!
-Jessica
Bug in Report Server?
I am running a report using RS2005. It connects to a web service using the XML data source. It works correctly in my development environment. When I put it up on the server and run the report, I get the error message:
If I run the web service from the server, it returns correct data, so I know error is not coming from my web service. The only answer I can think of is that there is a bug in the Report Server's or XML Data Source's code.
Has anyone else seen this problem?
Thank you,
Jessica
Hi Jessica, could you please repro the bug and send me most recent RS logs to almineev. At microsoft. Com.
RS logs are located at location similar to this one: C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\LogFiles
|||Jessica, did you ever find out the solution for your problem? I am experiencing a similar issue now.
Thanks,
James
|||It hapened to me, more or less the same.For what I know it can be a problem with the default values of the Report Parameters... they should not be originated by a query.
I had this problem and puting this as static or calculated values solved the issue...
Not the best way as by default the user's are not getting the data shown, but that's a solution.
Hope Microsoft solves the issue.. as this is a serious bug.
Regards,
Jose|||
Our problem was two report items on top of each other. Once we moved one of them over by just a little bit, the error went away.
I'm assuming it was something in the server code that wasn't handling the scenario of the same positional coordinates being inserted into a hash table, but that's just a guess.
We solved it by recreating the report one item at a time, uploading after each item. When we layered the second item on top of the first, that's when we received that message.
Good luck with everyone else trying to get this to work!
-Jessica
Bug in Report Server?
I am running a report using RS2005. It connects to a web service using the XML data source. It works correctly in my development environment. When I put it up on the server and run the report, I get the error message:
If I run the web service from the server, it returns correct data, so I know error is not coming from my web service. The only answer I can think of is that there is a bug in the Report Server's or XML Data Source's code.
Has anyone else seen this problem?
Thank you,
Jessica
Hi Jessica, could you please repro the bug and send me most recent RS logs to almineev. At microsoft. Com.
RS logs are located at location similar to this one: C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\LogFiles
|||Jessica, did you ever find out the solution for your problem? I am experiencing a similar issue now.
Thanks,
James
|||It hapened to me, more or less the same.For what I know it can be a problem with the default values of the
Report Parameters... they should not be originated by a query.
I had this problem and puting this as static or calculated values solved the issue...
Not the best way as by default the user's are not getting the data shown, but that's a solution.
Hope Microsoft solves the issue.. as this is a serious bug.
Regards,
Jose|||
Our problem was two report items on top of each other. Once we moved one of them over by just a little bit, the error went away.
I'm assuming it was something in the server code that wasn't handling the scenario of the same positional coordinates being inserted into a hash table, but that's just a guess.
We solved it by recreating the report one item at a time, uploading after each item. When we layered the second item on top of the first, that's when we received that message.
Good luck with everyone else trying to get this to work!
-Jessica
Bug in DATEDIFF?
I was curious if there is a bug in DATEDIFF when dealing with years. The
months seem to work correctly, but the Years are all over the place.
Here is some examples:
select
DATEDIFF(YEAR,'11/01/04','05/01/05'),DATEDIFF(MONTH,'11/01/04','05/01/05')
select
DATEDIFF(YEAR,'08/01/98','11/01/99'),DATEDIFF(MONTH,'08/01/98','11/01/99')
select
DATEDIFF(YEAR,'11/01/99','05/01/01'),DATEDIFF(MONTH,'11/01/99','05/01/01')
-- --
1 6 Should be 0 and 6
(1 row(s) affected)
-- --
1 15 Should be 0 and 15
(1 row(s) affected)
-- --
2 18 Should be 1 and 18
(1 row(s) affected)
Am I missing something?
Thanks,
Tom(a) never use such ambiguous date formats. I have no idea whether that
first date is November 1 2004, January 11 2004, January 4th 1911, or January
4th 2011. The server you are on is maybe guessing right, but what if you
run this code on a different server with different SET DATEFORMAT or regionl
settings?
(b) DATEDIFF(YEAR, measures the number of years that have passed. So,
DATEDIFF(YEAR, '20051231','20060101') = 1
DATEDIFF(YEAR, '20050101','20061231') = 1
This result is expected, and is not a bug. Basically, you can pretend that
it strips the month/day parts from the date (and time if that is supplied as
well), and just subtracts the integer derived from DATEPART(YEAR,
<dateValue> ).
If you're trying to calculate age based on birthdays, it's a little more
complex than a simple DATEDIFF.
http://www.aspfaq.com/2233
"tshad" <tscheiderich@.ftsolutions.com> wrote in message
news:e5bgY%23UFGHA.2204@.TK2MSFTNGP10.phx.gbl...
> Running on Sql Server 2000.
> I was curious if there is a bug in DATEDIFF when dealing with years. The
> months seem to work correctly, but the Years are all over the place.
> Here is some examples:
> select
> DATEDIFF(YEAR,'11/01/04','05/01/05'),DATEDIFF(MONTH,'11/01/04','05/01/05')
> select
> DATEDIFF(YEAR,'08/01/98','11/01/99'),DATEDIFF(MONTH,'08/01/98','11/01/99')
> select
> DATEDIFF(YEAR,'11/01/99','05/01/01'),DATEDIFF(MONTH,'11/01/99','05/01/01')
> -- --
> 1 6 Should be 0 and 6
> (1 row(s) affected)
>
> -- --
> 1 15 Should be 0 and 15
> (1 row(s) affected)
>
> -- --
> 2 18 Should be 1 and 18
> (1 row(s) affected)
> Am I missing something?
> Thanks,
> Tom
>|||There is no bug, it is working as it was meant to. All it does, I believe,
is take the year into account, does not do anything clever with the
respective position within each year.
"tshad" wrote:
> Running on Sql Server 2000.
> I was curious if there is a bug in DATEDIFF when dealing with years. The
> months seem to work correctly, but the Years are all over the place.
> Here is some examples:
> select
> DATEDIFF(YEAR,'11/01/04','05/01/05'),DATEDIFF(MONTH,'11/01/04','05/01/05')
> select
> DATEDIFF(YEAR,'08/01/98','11/01/99'),DATEDIFF(MONTH,'08/01/98','11/01/99')
> select
> DATEDIFF(YEAR,'11/01/99','05/01/01'),DATEDIFF(MONTH,'11/01/99','05/01/01')
> -- --
> 1 6 Should be 0 and 6
> (1 row(s) affected)
>
> -- --
> 1 15 Should be 0 and 15
> (1 row(s) affected)
>
> -- --
> 2 18 Should be 1 and 18
> (1 row(s) affected)
> Am I missing something?
> Thanks,
> Tom
>
>|||>> Am I missing something?
Yes, you are assuming DATEDIFF function on two dates returns the completed
year, month etc, which is not accurate.
DATEDIFF simply returns the number of date and time boundaries crossed
between two specified dates. And the results you got are consistent.
Anith|||select DATEDIFF(YEAR,'20051231','20060101'),
DATEDIFF(YEAR,'20050101','20051231')
Returns 1 and 0 even though in days, the first one is 1 day and the second
364 days.
DateDiff with years returns in reality the number of times January 1 is
"crossed".
This is what BOL has to say:
"Returns the number of date and time boundaries crossed between two
specified dates."
This is true for Datediff with years, months, w
"tshad" <tscheiderich@.ftsolutions.com> wrote in message
news:e5bgY%23UFGHA.2204@.TK2MSFTNGP10.phx.gbl...
> Running on Sql Server 2000.
> I was curious if there is a bug in DATEDIFF when dealing with years. The
> months seem to work correctly, but the Years are all over the place.
> Here is some examples:
> select
> DATEDIFF(YEAR,'11/01/04','05/01/05'),DATEDIFF(MONTH,'11/01/04','05/01/05')
> select
> DATEDIFF(YEAR,'08/01/98','11/01/99'),DATEDIFF(MONTH,'08/01/98','11/01/99')
> select
> DATEDIFF(YEAR,'11/01/99','05/01/01'),DATEDIFF(MONTH,'11/01/99','05/01/01')
> -- --
> 1 6 Should be 0 and 6
> (1 row(s) affected)
>
> -- --
> 1 15 Should be 0 and 15
> (1 row(s) affected)
>
> -- --
> 2 18 Should be 1 and 18
> (1 row(s) affected)
> Am I missing something?
> Thanks,
> Tom
>|||"Lee" <Lee@.discussions.microsoft.com> wrote in message
news:B4D02445-41D7-43CC-B570-DF88B181FF3C@.microsoft.com...
> There is no bug, it is working as it was meant to. All it does, I
> believe,
> is take the year into account, does not do anything clever with the
> respective position within each year.
If that is the case, it is relatively useless.
I am not actually passing the literal date as shown, but 2 smalldatetime
fields from my table.
But 6 months does not equal a year and 18 months doesn't equal a 2 years.
If what you are saying is true about just looking at the year, why then does
not the MONTH calculation look only at the months. It does calculate
correctly.
Here is a calculation that is 7 days apart, so months should be 0 and it is:
select
DATEDIFF(YEAR,'11/01/99','11/05/99'),DATEDIFF(MONTH,'11/01/99','11/08/99')
-- --
0 0
(1 row(s) affected)
> "tshad" wrote:
>|||"Aaron Bertrand [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
news:uLu6kFVFGHA.3120@.TK2MSFTNGP10.phx.gbl...
> (a) never use such ambiguous date formats. I have no idea whether that
> first date is November 1 2004, January 11 2004, January 4th 1911, or
> January 4th 2011. The server you are on is maybe guessing right, but what
> if you run this code on a different server with different SET DATEFORMAT
> or regionl settings?
>
I am not using ambiguous formats. This was just for demonstration. I am
actually using fields from my table:
DATEDIFF(YEAR,FromDate,ToDate) (FromDate and ToDate are DateTime
fields)
> (b) DATEDIFF(YEAR, measures the number of years that have passed. So,
> DATEDIFF(YEAR, '20051231','20060101') = 1
> DATEDIFF(YEAR, '20050101','20061231') = 1
> This result is expected, and is not a bug. Basically, you can pretend
> that it strips the month/day parts from the date (and time if that is
> supplied as well), and just subtracts the integer derived from
> DATEPART(YEAR, <dateValue> ).
>
If not a bug, definately makes no sense to me as to what usefulness it would
be.
> If you're trying to calculate age based on birthdays, it's a little more
> complex than a simple DATEDIFF.
> http://www.aspfaq.com/2233
>
>
> "tshad" <tscheiderich@.ftsolutions.com> wrote in message
> news:e5bgY%23UFGHA.2204@.TK2MSFTNGP10.phx.gbl...
>|||"Anith Sen" <anith@.bizdatasolutions.com> wrote in message
news:OWHP%23HVFGHA.3892@.TK2MSFTNGP12.phx.gbl...
> Yes, you are assuming DATEDIFF function on two dates returns the completed
> year, month etc, which is not accurate.
> DATEDIFF simply returns the number of date and time boundaries crossed
> between two specified dates. And the results you got are consistent.
No.
I would agree if MONTH worked the same way, but as I mentioned in another
response, but MONTH does work correctly.
What you should get is 0 years for 0-11 months and 1 for 1-12 months.
Subtracting the years makes no sense - at least as far as I can fathom.
Thanks,
Tom
> --
> Anith
>|||> But 6 months does not equal a year and 18 months doesn't equal a 2 years.
If you're interested in the number of months that have passed, then use
MONTH instead of YEAR as the argument to DATEDIFF.
> Here is a calculation that is 7 days apart, so months should be 0 and it
> is:
> select
> DATEDIFF(YEAR,'11/01/99','11/05/99'),DATEDIFF(MONTH,'11/01/99','11/08/99')
I'm not sure I understand your argument. Of course both return 0 -- you
have not crossed into a new month, nor have you crossed into a new year.
How about :
SELECT DATEDIFF(MONTH, '19991031', '19991101');
SELECT DATEDIFF(MONTH, '19991001', '19991130');
SELECT DATEDIFF(MONTH, '19991231', '20000101');
Gee, all of those return 1. In the first case, only 1 day has passed; in
the second case, almost 2 months have passed; and, in the third case, we've
crossed into a new year.
Should SQL Server guess what each one of us would consider a threshold for
the difference in those dates being anything other than 1 month? Do you
round up starting at 15 days, 28 days, 30 days, 31 days? What if it's
February and you're crossing a leap year? What about Daylight Savings Time?
What if the groundhog does't see his shadow? DATEDIFF is based on the
simple parts of a date, it is not a mind reader.|||(2005 - 2004) = 1
(2004-2005) = -1
(2005 - 2005) = 0
It is just working with the integer year numbers, no fancy date
calculations. What are you actually needing?
William Stacey [MVP]
"tshad" <tscheiderich@.ftsolutions.com> wrote in message
news:%23pD85lVFGHA.216@.TK2MSFTNGP15.phx.gbl...
> My mistake on the MONTH ( I was actually using Days in my example on
> Months)
> But I see no use for the YEAR DATEDIFF ( I am sure there is some use, but
> to say 1 month and 15 months are both 1 year makes no sense)
> Tom
> "Raymond D'Anjou" <rdanjou@.canatradeNOSPAM.com> wrote in message
> news:%232DO9JVFGHA.1288@.TK2MSFTNGP09.phx.gbl...
>
Friday, February 24, 2012
Browser Compatibility in SSRS 2005
The report displays squished to the left side of the browser as it did in SSRS 2000.
Is it the viewer that does this or a setting I need to set?
I am running my report from a URL.
Also seems to open ok if I export to PDF.
Does not work in HTML view.Check sizes of report items in your report and CanShrink/CanGrow properties. If they are set incorrectly in most cases IE will still show them right. Firefox is picky.|||Thanks that was it
|||
I need suggestions regarding the report being viewed in firefox:
Problem:
In Matrix reports the "sub Total" Columnm is getting wrapped to .0001 in (Probably!!!!! not to that accuracy), But i can see the remaining part like Row and Column Cells r displaying properly.
only the Last Column is being truncated..
This happens only in FireFox But not in IE.
Required Result:
"Sub Total" column also has to be seen clearly as other cells.
Any Suggestions?
Regards,
Sri Harsha Kasi
Browser Compatibility in SSRS 2005
The report displays squished to the left side of the browser as it did in SSRS 2000.
Is it the viewer that does this or a setting I need to set?
I am running my report from a URL.
Also seems to open ok if I export to PDF.
Does not work in HTML view.Check sizes of report items in your report and CanShrink/CanGrow properties. If they are set incorrectly in most cases IE will still show them right. Firefox is picky.|||Thanks that was it|||
I need suggestions regarding the report being viewed in firefox:
Problem:
In Matrix reports the "sub Total" Columnm is getting wrapped to .0001 in (Probably!!!!! not to that accuracy), But i can see the remaining part like Row and Column Cells r displaying properly.
only the Last Column is being truncated..
This happens only in FireFox But not in IE.
Required Result:
"Sub Total" column also has to be seen clearly as other cells.
Any Suggestions?
Regards,
Sri Harsha Kasi
Browser Compatibility in SSRS 2005
The report displays squished to the left side of the browser as it did in SSRS 2000.
Is it the viewer that does this or a setting I need to set?
I am running my report from a URL.
Also seems to open ok if I export to PDF.
Does not work in HTML view.Check sizes of report items in your report and CanShrink/CanGrow properties. If they are set incorrectly in most cases IE will still show them right. Firefox is picky.|||Thanks that was it
|||
I need suggestions regarding the report being viewed in firefox:
Problem:
In Matrix reports the "sub Total" Columnm is getting wrapped to .0001 in (Probably!!!!! not to that accuracy), But i can see the remaining part like Row and Column Cells r displaying properly.
only the Last Column is being truncated..
This happens only in FireFox But not in IE.
Required Result:
"Sub Total" column also has to be seen clearly as other cells.
Any Suggestions?
Regards,
Sri Harsha Kasi
Friday, February 10, 2012
Borders on Cells Not Rendering Correctly
> of cells. It looks great when viewing it in Report Manager; however
> (there is always a however) when I print the report some borders are
> thin and of a lighter weight than they should be.
> My cells have a 0 padding, so I thought was an issue. I changed the
> padding to 2pt - no luck.
> Any ideas? Any work-arounds? Is this an 'undocumented feature'?
Some things to try:
If you have the borders defined on one side and not the other (in other
words, the cell on the left has a right border defined) then try
setting the left border for the cell on the right.
If you have both borders defined as described above, try turning off
one or the other.
Yes, I realize those two things are contradictory, but I've personally
had times when one worked and not the other for whatever magical
reason.
I've also had cases where setting the background color to "white"
instead of "transparent" helped - and vice versa. I've had cases where
alternating the background color of rows causes the problem.
Basically, just tinker with the settings and hope for the best.having the same problems - anyone find any solutions? Can someone from
Msoft confirm there are issues with this functionaility?
cphite@.hotmail.com wrote:
> > I am creating a report where I need to create a border around a series
> > of cells. It looks great when viewing it in Report Manager; however
> > (there is always a however) when I print the report some borders are
> > thin and of a lighter weight than they should be.
> > My cells have a 0 padding, so I thought was an issue. I changed the
> > padding to 2pt - no luck.
> > Any ideas? Any work-arounds? Is this an 'undocumented feature'?
> Some things to try:
> If you have the borders defined on one side and not the other (in other
> words, the cell on the left has a right border defined) then try
> setting the left border for the cell on the right.
> If you have both borders defined as described above, try turning off
> one or the other.
> Yes, I realize those two things are contradictory, but I've personally
> had times when one worked and not the other for whatever magical
> reason.
> I've also had cases where setting the background color to "white"
> instead of "transparent" helped - and vice versa. I've had cases where
> alternating the background color of rows causes the problem.
> Basically, just tinker with the settings and hope for the best.
Borders on Cells Not Rendering Correctly
of cells. It looks great when viewing it in Report Manager; however
(there is always a however) when I print the report some borders are
thin and of a lighter weight than they should be.
My cells have a 0 padding, so I thought was an issue. I changed the
padding to 2pt - no luck.
Any ideas? Any work-arounds? Is this an 'undocumented feature'?Yeah, I get the same thing sometimes when I export to PDF. Normally it's
because of overlapping report items that don't appear to be overlapping in
the designer. If I select the two items and use menu (Formatting, Vertical
Spacing, Remove Vertical Spacing), it fixes my issues. Hope this helps.
Steve MunLeeuw
"JJodon" <jjodon@.gmail.com> wrote in message
news:1156511711.319480.225930@.p79g2000cwp.googlegroups.com...
>I am creating a report where I need to create a border around a series
> of cells. It looks great when viewing it in Report Manager; however
> (there is always a however) when I print the report some borders are
> thin and of a lighter weight than they should be.
> My cells have a 0 padding, so I thought was an issue. I changed the
> padding to 2pt - no luck.
> Any ideas? Any work-arounds? Is this an 'undocumented feature'?
>|||Thanks for the reply, Steve.
I see what you me in regards to two objects (a subreport and a table);
however Imy issues are with cells in the same table. I tried your trick
and the Horz. and Vert. Spacing options are not available.
Steve MunLeeuw wrote:
> Yeah, I get the same thing sometimes when I export to PDF. Normally it's
> because of overlapping report items that don't appear to be overlapping in
> the designer. If I select the two items and use menu (Formatting, Vertical
> Spacing, Remove Vertical Spacing), it fixes my issues. Hope this helps.
> Steve MunLeeuw
>|||Has anybody else found a solution to this problem? I am having the exact
same results with borders in a table. Some of the detail rows have different
border widths than others. That doesn't make any sense.
BJ
"JJodon" wrote:
> Thanks for the reply, Steve.
> I see what you me in regards to two objects (a subreport and a table);
> however Imy issues are with cells in the same table. I tried your trick
> and the Horz. and Vert. Spacing options are not available.
>
> Steve MunLeeuw wrote:
> > Yeah, I get the same thing sometimes when I export to PDF. Normally it's
> > because of overlapping report items that don't appear to be overlapping in
> > the designer. If I select the two items and use menu (Formatting, Vertical
> > Spacing, Remove Vertical Spacing), it fixes my issues. Hope this helps.
> >
> > Steve MunLeeuw
> >
>|||Same problem here! I can find very few reported incidents of this anywhere -
if anyone can shed some light on this problem, please do.
"bjkaledas" wrote:
> Has anybody else found a solution to this problem? I am having the exact
> same results with borders in a table. Some of the detail rows have different
> border widths than others. That doesn't make any sense.
> BJ
> "JJodon" wrote:
> > Thanks for the reply, Steve.
> >
> > I see what you me in regards to two objects (a subreport and a table);
> > however Imy issues are with cells in the same table. I tried your trick
> > and the Horz. and Vert. Spacing options are not available.
> >
> >
> > Steve MunLeeuw wrote:
> > > Yeah, I get the same thing sometimes when I export to PDF. Normally it's
> > > because of overlapping report items that don't appear to be overlapping in
> > > the designer. If I select the two items and use menu (Formatting, Vertical
> > > Spacing, Remove Vertical Spacing), it fixes my issues. Hope this helps.
> > >
> > > Steve MunLeeuw
> > >
> >
> >|||If you post a sample report I can see if I reproduce on my machine.
Steve MunLeeuw
"JJodon" <jjodon@.gmail.com> wrote in message
news:1156511711.319480.225930@.p79g2000cwp.googlegroups.com...
>I am creating a report where I need to create a border around a series
> of cells. It looks great when viewing it in Report Manager; however
> (there is always a however) when I print the report some borders are
> thin and of a lighter weight than they should be.
> My cells have a 0 padding, so I thought was an issue. I changed the
> padding to 2pt - no luck.
> Any ideas? Any work-arounds? Is this an 'undocumented feature'?
>