layout problem

Hi,
I have 4 subreports in a report and adjust thier position well on layout
tag.
Preview on the report designer everything is fine.
But deploy to report server and browse on IE the subreports all on the wrong
position!
How can I resolve this problem?
Thanks for help!
AngiI had the same problem with some of my reports I found out the only way
ot get the layout right is to enter the location for each item on the
report in the location property and " measure/space" so nothing is over
laping. One can begin where one ends but if they overlap the location
it will be moved to onther page. It still looks a little funny on the
browser but it prints perfectly.sql

latency

Can someone please describe what this is and how I adjust my dist cleanup
agent retention times for it.
I know the basics, but when I go into MSdistribution table there are alot of
fields that seem similiar (ie: current_delivery_rate,
current_delivery_latency, delivery_rate, delivery_latency). Can someone
please explain the differences between these? And also how I can look at
bottlenecks that are increasing the latency and how do I find out my average
latency time for a specified period to valid the improvements?
Thanks,
K
P.S. I just received HC's book, so if someone could direct me to a location
in there, that would be fine too.
Latency is the average amount of time required for a transaction to be
applied on the subscriber after it has been applied on the publisher.
Current_delivery_rate is the Average number of commands delivered per second
since the distribution agent last ran. Current_delivery_latency is the
Latency between the command entering the distribution database and being
applied to the Subscriber since the last history entry.
If your Distribution agent runs in intervals or is scheduled latency can be
lengthy.
delivery_rate is average commands per second.
Recall that a transaction applied on the publisher is broken down to
singletons. So that a transaction which updates 100 rows will be transformed
into 100 update commands. So if you have a lot of singleton transactions
your delivery rate will be higher than if you have a lot of batch processes
which will mean a higher number of commands and a lower delivery rate.
Delivery_latency is Latency between the command entering the distribution
database and being applied to the Subscriber.
So, the lower your polling interval and if your distribution agent is
running continuously these values should be the same.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Kristy" <pleasereplyby@.posting.com> wrote in message
news:Ocmi8LBJFHA.3376@.TK2MSFTNGP14.phx.gbl...
> Can someone please describe what this is and how I adjust my dist cleanup
> agent retention times for it.
> I know the basics, but when I go into MSdistribution table there are alot
of
> fields that seem similiar (ie: current_delivery_rate,
> current_delivery_latency, delivery_rate, delivery_latency). Can someone
> please explain the differences between these? And also how I can look at
> bottlenecks that are increasing the latency and how do I find out my
average
> latency time for a specified period to valid the improvements?
> Thanks,
> K
> P.S. I just received HC's book, so if someone could direct me to a
location
> in there, that would be fine too.
>