Where do you get this limit??? You can disable the limit on number of rows
completely by going into file/parameters/… tab and disable it.
Aultman, Steven (SMAU) schrieb:
Does anyone know if there is a way around this limit?
I’m using (still converting to) version 4.1.2 for WinNT against a Sybase 11.x database.
Well, this seems to be a FAQ… I have asked it two weeks ago. The reason is, there is an option in Tools/Options , Database tab, called “Maximum Number of Rows Fetched”,
which is , in fact, limited to 10000 (5000 in BO 4.1.1). I don’t remember, what is it used for (there were at least two different explanations ), but I know by now it has nothing to do with maximum number of rows fetched as a result of query. It is really misleading…
Well, this seems to be a FAQ… I have asked it two weeks ago. The reason is, there is an option in Tools/Options , Database tab, called “Maximum Number of Rows Fetched”,
which is , in fact, limited to 10000 (5000 in BO 4.1.1). I don’t remember, what is it used for (there were at least two different explanations ), but I know by now it has nothing to do with maximum number of rows fetched as a result of query. It is really misleading… …
The option under in Tools->Options, in the Database tab is in a box marked “Table and Column values”. What this means, is that it is the maximum number of values Designer will display if you view the table or column values (by either right clicking and selecting “View Table/column values” or selecting “Table values” from the view menu). It is only applicable to Designer and has absolutely nothing to do with the underlying configuration of the Universe. Note that if you are unfamilar with the ability to view table or column values, look in Help under “Viewing the values in a column” or “Viewing the values in a table.”
Well, this seems to be a FAQ… I have asked it two weeks ago. The reason is, there is an option in Tools/Options , Database tab, called “Maximum Number of Rows Fetched”,
which is , in fact, limited to 10000 (5000 in BO 4.1.1). I don’t remember, what is it used for (there were at least two different explanations ), but I know by now it has nothing to do with maximum number of rows fetched as a result of query. It is really misleading…
This tools/options limit is the number of rows fetched when right-clicking in the table in structure window of designer and retrieving rows of the table… It HAS NOTHING TO DO with query limits in the reporter module.
Hope this helps, W.
DI Walter Muellner
Delphi Software GmbH, Vivenotgasse 48, A-1120 Vienna / Austria Tel: +43-1-8151456-12, Fax: +43-1-8151456-21 e-mail: w.muellner@delphi.at, WEB: http://www.delphi.at
There are two places in Designer where you can specify a maximum number of rows fetched.
Tools|Options|Database|Maximum Number of Rows fetched. This
setting is available when no universe is loaded. So it has nothing to do with a the universe and is only used when peeking at table values in the designer. I think it is also used when detecting joins, but I’m not sure of this.
setting is only available for a universe. It specifies the maximum number of rows fetched when creating a report based on the universe. If the limit is reached in Reporter a flashing yellow triangle at the bottom bar shows that the current report was not based on complete data. The other reason for not having complete data is when the execution time limit is reached.
There are two places in Designer where you can specify a maximum number of rows fetched.
Tools|Options|Database|Maximum Number of Rows fetched. This
setting is available when no universe is loaded. So it has nothing to do with a the universe and is only used when peeking at table values in the designer. I think it is also used when detecting joins, but I’m not sure of this.
setting is only available for a universe. It specifies the maximum number of rows fetched when creating a report based on the universe. If the limit is reached in Reporter a flashing yellow triangle at the bottom bar shows that the current report was not based on complete data. The other reason for not having complete data is when the execution time limit is reached.
Yes, now I know everything, that all of you have kindly written, thank you. My only remark was, that option name Tools|Options|Database is misleading, thus making a question “How to avoid 10.000 limit on a query?” a FAQ… Even BO help for this option says:
Tables and Columns values
Maximum number of lines fetched
Lets you set the maximum number of rows that can be returned from the database. By default, the value is 100.
Copyright (C) 1990-1998 Business Objects
… which does not clear anything.
Maybe they will at least change the help text in some next release? Just a little wish…