All

Is there a way to change the format of a SCHEDULE that was submitted .

For example ,

I have a Daily schedule submitted with the format as XL . As far as it is retrieving less than 65000 rows i am ok. But if it is going to retrieve more than 65000 rows, then thats a problem for me.

So based on the rows i want to change the format as XL or CSV.

Is there a way anyone think off..

Preprocess the data and set a variable to the foramt that you wish to use depending upon the value of &LINES.

Then have ON TABLE HOLD FORMAT &variablename.

T

The problem is that you have to specify the format of the output file in Caster and (according to the docs) that format overrides anything you put in the fex. There might not be a good solution for this one.

Darin

My Plan is to

1. Run the query . Identify the total number of rows returned.
2. If the total rows is more than 65K , then update the BOTTASK table's SENDFORMAT column for the particular schedule.

willl this be good ??

I would create the CSV file in all cases.

Once you have the output file you can open it in EXCEL if it has less then 65000 rows.
You can put an inline report that warns you if you have more than 65K records.

Frank ,

Actually , the requirement is basically XL.
So we go create an XL , but we have many instances which have more than 65K rows. SO we would like to apply some intelligence so that based on the rows , the schedule creates the file either in XL or CSV.

Navin
have your fex put out a 2-sheet exl2k, the first 65k on sheet 1 and the remainder on sheet 2.
Your users have enough memory in their desktops to open 65k? mine sure don't.

quote:

My Plan is to

1. Run the query . Identify the total number of rows returned.
2. If the total rows is more than 65K , then update the BOTTASK table's SENDFORMAT column for the particular schedule.

The problem would be this: If you put these steps as part of the preprocess sequence, then the scheduled job has already been executed and if you change the sendformat after the fact, it would make no difference in the current job. you could schedule the job twice, but if your data is very dynamic, there's absolutely no guarantee that your result sets would be the same. For example, if the scheduled job executed resulting in less than 65k rows, the next job runs a minute later but the data has changed and there are now more than 65k rows.

You really don't have a good option with ReportCaster except to break it into spearate worksheets as susannah suggests. There are multiple posts regarding this technique if you use the search tab.

You could also have users upgrade their Excel version to 2007 where the 65k row limit has been raised to 2 million or something like that.

Last comment - IMO, reports that have over 65000 rows are not "reports" but data extracts and should handled in processes that treat them as such. There's my "soapbox" statement for the day. (Maybe)