Page Break after a value in one of the report groups

There are 3 groups in my reportâ' grp1, grp2 and grp3, with grp1 at the top,
grp2 in the middle and grp3 at the bottom. I need to insert a page break when
the value of grp1 record becomes â'abcâ'. Is this possible? If so, I will
really appreciate if someone can let me know how.
Thanks in advance,
SauravDid you ever find out how to do this? I need a page break in a report just
like you are descibing.
Thanks
"sajmera" wrote:
> There are 3 groups in my reportâ' grp1, grp2 and grp3, with grp1 at the top,
> grp2 in the middle and grp3 at the bottom. I need to insert a page break when
> the value of grp1 record becomes â'abcâ'. Is this possible? If so, I will
> really appreciate if someone can let me know how.
> Thanks in advance,
> Saurav
>sql

page break

I have a matrix and I want to insert a page break on a column group. I dont
see the option under grouping and sorting properties for my column groups
only on the rows?On Nov 2, 10:39 am, RYF <R...@.discussions.microsoft.com> wrote:
> I have a matrix and I want to insert a page break on a column group. I dont
> see the option under grouping and sorting properties for my column groups
> only on the rows?
Unfortunately, this functionality does not exist currently. A
workaround would be to create 2 matrices/matrix controls in the report
and have the columns you want on the odd pages in the first matrix
control (and do a page break after it) and the columns you want on the
even pages in the second matrix control (and do a page break after it
as well). Sorry that I could not be of greater assistance.
Regards,
Enrique Martinez
Sr. Software Consultant

package goes into loop while reading paradox file

I have an SSIS package which is suppose to read this db file and insert it into the SQL 2005 table. But when I execute this package it goes into a loop, reading the file over and over again. The package fails after inserting some 10 million rows ( actual rows are not more then 270,000) giving the error msg'Not enough space on temporary disk'.

On examing the data transfered into SQL there are duplicate rows.

I also used the import export wizard (thinking there might be some error in Package code) provided by SQL to transfer the data from .db to SQL but it has the same result(goes in a loop).

I would appreciate any help in this problem. Let me know if you have any other questions.

Thanks

Do you have anything except the source and the destination in your package?

Thanks.

|||

If incase you are successful extracting 5-10 rows from a paradox file, The same must do for 270000 as well. Please also check if ending rows were corrupt.

|||

Hello Bob,

The package which I have created has source, conversion and destination components. The conversion component converts nvarchar field to varchar. This package works on another .db file say file 'YYY.db'. but then fails to read file 'ZZZ.db'.

The file does not seem to be corrupted coz when I try to view it through a paradox viewer it gives me the correct record count, field names etc and also displays the data correctly. We also have another viewer through which the file attributes and data are correctly displayed. Therefore it seems that ZZZ.db is not corrupted. The package also reads the file but then it fails to stop reading, seems as if it thinks there is no end of file. But the other independent viewers are able to read the file.

My computer does have the latest updates. Any ideas/suggestions/thoughts would be greatly appreciated.

Thanks,

Smoky

Overwriting entry in table

Task:

To insert entries into a table. The table has a primary key based on a field 'ID'. When inserting into the destination table, I want to make sure that the new entry will overwrite the old entry.

What's the quickest/cleaniest way to do this ?

thanks,
ClaytonUPDATE <table>
SET <column>=<value>, etc...
WHERE field_id = <field_id>

Overlapping Trigger Precedence

Hi,
What is the execution precedence if there exist more than one update, delete
or insert triggers
I mean if there are more than one type of trigger such as more than one
update trigger.
Also, Can we specify a precedence for them?
and last If we call an update statement in the same update trigger and for
the same table that has this trigger, Is the trigger considers itself, I
mean is it recurs or not, or is it disables itself for that execution period
?.
Thanks in advance...
Emre GuldoganThere is no guarantee as to what order they'll fire in.
Adam Machanic
SQL Server MVP
http://www.sqljunkies.com/weblog/amachanic
--
"Emre Guldogan" <ask me please...> wrote in message
news:e$KbhKMJFHA.656@.TK2MSFTNGP14.phx.gbl...
> Hi,
> What is the execution precedence if there exist more than one update,
delete
> or insert triggers
> I mean if there are more than one type of trigger such as more than one
> update trigger.
> Also, Can we specify a precedence for them?
> and last If we call an update statement in the same update trigger and for
> the same table that has this trigger, Is the trigger considers itself, I
> mean is it recurs or not, or is it disables itself for that execution
period
> ?.
> Thanks in advance...
> Emre Guldogan
>|||You can use sp_settriggerorder to define the first and last trigger to
execute. For the rest the order is undefined. If it matters to you then
put all the logic in one trigger.
David Portas
SQL Server MVP
--|||On Wed, 9 Mar 2005 18:11:48 +0200, "Emre Guldogan" <ask me please...>
wrote:

>What is the execution precedence if there exist more than one update, delet
e
>or insert triggers
>I mean if there are more than one type of trigger such as more than one
>update trigger.
>Also, Can we specify a precedence for them?
Hi Emre,
Already addressed by David and Adam.

>and last If we call an update statement in the same update trigger and for
>the same table that has this trigger, Is the trigger considers itself, I
>mean is it recurs or not, or is it disables itself for that execution perio
d
>?.
There are two options governing this:
1. Recursive triggers. If this is off, a trigger can't fire itself. So
if an update trigger on table AA performans an UPDATE AA command, that
specific trigger is not called. This disables only direct recursion: if
the update trigger on AA performs a DELETE FROM BB statement, and the
delete trigger on BB performs UPDATE AA, the trigger will be called
recursively.
The recursive triggers option is a database setting: it will affect all
triggers in the current database, but it won't affect other databases on
the same server. You use ALTER DATABASE to change it.
2. Nested triggers. If this is off, statements executed from a trigger
don't fire any trigger at all.
The nested triggers option is a server setting: it will affect all
triggers in all databases on the server. You use sp_configure to change
it.
Other options to prevent recursive execution of triggers for specific
triggers only are:
* TRIGGER_NESTLEVEL() - check this to find how many nested trigger
executions there currently are.
* TRGIGER_NESTLEVEL(object_ID('trigger_nam
e')) - check this to find how
many times the specified trigger is currently nested.
Best, Hugo
--
(Remove _NO_ and _SPAM_ to get my e-mail address)