Sybase NNTP forums - End Of Life (EOL)

The NNTP forums from Sybase - forums.sybase.com - are now closed.

All new questions should be directed to the appropriate forum at the SAP Community Network (SCN).

Individual products have links to the respective forums on SCN, or you can go to SCN and search for your product in the search box (upper right corner) to find your specific developer center.

Computed field limit

5 posts in PB Infomaker Report Writer Last posting was on 1999-05-05 11:51:29.0Z
Doreen Weekley Posted on 1999-04-30 11:27:57.0Z
Newsgroups: sybase.public.infomaker.general
From: "Doreen Weekley" <dweekley@primavera.com>
Subject: Computed field limit
Date: Fri, 30 Apr 1999 07:27:57 -0400
Lines: 13
X-Newsreader: Microsoft Outlook Express 4.72.3110.5
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3
Message-ID: <348_nUkDitvk#GA.223@forums.sybase.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.infomaker.general:6384
Article PK: 241370

I think I read a response that indicated there was a fixed number of
allowable
computed fields in a report. I use a lot of them on some reports and have
noticed some strange behavior and now wonder if I'm exceeding the limit in
these cases. For version 6.5 what is the allowable number? I'm sure that
complexity comes into play as it will affect resources but if there are
other guidelines that are known, like limits to nesting, would you please
point me to where I might find those.

Tks
Doreen


Terry Dykstra Posted on 1999-04-30 15:35:52.0Z
Newsgroups: sybase.public.infomaker.general
From: "Terry Dykstra" <tdykstra@cfol.ab.ca>
Subject: Re: Computed field limit
Date: Fri, 30 Apr 1999 09:35:52 -0600
Lines: 25
X-Newsreader: Microsoft Outlook Express 4.72.3110.5
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3
Message-ID: <348_5VP$Q6xk#GA.322@forums.sybase.com>
References: <348_nUkDitvk#GA.223@forums.sybase.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.infomaker.general:6382
Article PK: 241367

As far as I know, there are no hardcoded limits. Generally speaking you
will be able to do more under NT, since it has better memory management than
W95. If I find out more, I'll let you know.
Out of curiosity, how many computed fields and / or nested reports do you
have?

--
Terry Dykstra (TeamPS)
Canadian Forest Oil Ltd.

Doreen Weekley wrote in message ...
>I think I read a response that indicated there was a fixed number of
>allowable
>computed fields in a report. I use a lot of them on some reports and have
>noticed some strange behavior and now wonder if I'm exceeding the limit in
>these cases. For version 6.5 what is the allowable number? I'm sure that
>complexity comes into play as it will affect resources but if there are
>other guidelines that are known, like limits to nesting, would you please
>point me to where I might find those.
>
>Tks
>Doreen
>
>


Doreen Weekley Posted on 1999-05-04 17:03:50.0Z
Newsgroups: sybase.public.infomaker.general
From: "Doreen Weekley" <dweekley@primavera.com>
Subject: Re: Computed field limit
Date: Tue, 4 May 1999 13:03:50 -0400
Lines: 52
X-Newsreader: Microsoft Outlook Express 4.72.3110.5
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3
Message-ID: <348_D#xf37kl#GA.263@forums.sybase.com>
References: <348_nUkDitvk#GA.223@forums.sybase.com> <348_5VP$Q6xk#GA.322@forums.sybase.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.infomaker.general:6372
Article PK: 241360

Hi Terry:

Actually I don't need a lot of nested reports. I was referring more to
nesting functions as
a simple example: if (a,b,c) where b and c might be another if statement.
We often have to parse, manipulate and perform calculations before
interpreting the data from the files so
it leads to some nesting of functions in the calculated fields that can get
ugly. We try to
keep all this on the report, instead of db, side to make it easier for the
user to understand.
To answer your question about how may computed fields, we may use 15 - 32
per report. Probably half of those are used only because these reports have
to act as templates and since I have not been successful getting alias names
to work w/multiple tables we use a computed field in place of the column
just so it doesn't drop off the report when the table names change. The
other half are the result of the ugly calculations/manipulations that are
required by the data.

Tks for your help
Doreen

Terry Dykstra wrote in message <5VP$Q6xk#GA.322@forums.sybase.com>...
>As far as I know, there are no hardcoded limits. Generally speaking you
>will be able to do more under NT, since it has better memory management
than
>W95. If I find out more, I'll let you know.
>Out of curiosity, how many computed fields and / or nested reports do you
>have?
>
>--
>Terry Dykstra (TeamPS)
>Canadian Forest Oil Ltd.
>Doreen Weekley wrote in message ...
>>I think I read a response that indicated there was a fixed number of
>>allowable
>>computed fields in a report. I use a lot of them on some reports and have
>>noticed some strange behavior and now wonder if I'm exceeding the limit in
>>these cases. For version 6.5 what is the allowable number? I'm sure that
>>complexity comes into play as it will affect resources but if there are
>>other guidelines that are known, like limits to nesting, would you please
>>point me to where I might find those.
>>
>>Tks
>>Doreen
>>
>>
>
>


Terry Dykstra Posted on 1999-05-04 18:16:34.0Z
Newsgroups: sybase.public.infomaker.general
From: "Terry Dykstra" <tdykstra@cfol.ab.ca>
Subject: Re: Computed field limit
Date: Tue, 4 May 1999 12:16:34 -0600
Lines: 65
X-Newsreader: Microsoft Outlook Express 4.72.3110.5
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3
Message-ID: <348_F#xKDnll#GA.300@forums.sybase.com>
References: <348_nUkDitvk#GA.223@forums.sybase.com> <348_5VP$Q6xk#GA.322@forums.sybase.com> <348_D#xf37kl#GA.263@forums.sybase.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.infomaker.general:6370
Article PK: 241356

Take a look at the CASE statement. It is easier than nested IFs.

--
Terry Dykstra (TeamPS)
Canadian Forest Oil Ltd.

Doreen Weekley wrote in message ...
>Hi Terry:
>
>Actually I don't need a lot of nested reports. I was referring more to
>nesting functions as
>a simple example: if (a,b,c) where b and c might be another if statement.
>We often have to parse, manipulate and perform calculations before
>interpreting the data from the files so
>it leads to some nesting of functions in the calculated fields that can get
>ugly. We try to
>keep all this on the report, instead of db, side to make it easier for the
>user to understand.
>To answer your question about how may computed fields, we may use 15 - 32
>per report. Probably half of those are used only because these reports
have
>to act as templates and since I have not been successful getting alias
names
>to work w/multiple tables we use a computed field in place of the column
>just so it doesn't drop off the report when the table names change. The
>other half are the result of the ugly calculations/manipulations that are
>required by the data.
>
>Tks for your help
>Doreen
>
>
>Terry Dykstra wrote in message <5VP$Q6xk#GA.322@forums.sybase.com>...
>>As far as I know, there are no hardcoded limits. Generally speaking you
>>will be able to do more under NT, since it has better memory management
>than
>>W95. If I find out more, I'll let you know.
>>Out of curiosity, how many computed fields and / or nested reports do you
>>have?
>>
>>--
>>Terry Dykstra (TeamPS)
>>Canadian Forest Oil Ltd.
>>Doreen Weekley wrote in message ...
>>>I think I read a response that indicated there was a fixed number of
>>>allowable
>>>computed fields in a report. I use a lot of them on some reports and
have
>>>noticed some strange behavior and now wonder if I'm exceeding the limit
in
>>>these cases. For version 6.5 what is the allowable number? I'm sure
that
>>>complexity comes into play as it will affect resources but if there are
>>>other guidelines that are known, like limits to nesting, would you please
>>>point me to where I might find those.
>>>
>>>Tks
>>>Doreen
>>>
>>>
>>
>>
>
>


Doreen Weekley Posted on 1999-05-05 11:51:29.0Z
Newsgroups: sybase.public.infomaker.general
From: "Doreen Weekley" <dweekley@primavera.com>
Subject: Re: Computed field limit
Date: Wed, 5 May 1999 07:51:29 -0400
Lines: 78
X-Newsreader: Microsoft Outlook Express 4.72.3110.5
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3
Message-ID: <348_IVifAyul#GA.290@forums.sybase.com>
References: <348_nUkDitvk#GA.223@forums.sybase.com> <348_5VP$Q6xk#GA.322@forums.sybase.com> <348_D#xf37kl#GA.263@forums.sybase.com> <348_F#xKDnll#GA.300@forums.sybase.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.infomaker.general:6367
Article PK: 241353

Actually I over simplified my example. You're right about the case statement
and I use it when
I can but usually the reason I nest is to parse, concatenate, convert data
types, sometimes do a mathematical calc and so on within one computed field.

Tks
Doreen

Terry Dykstra wrote in message ...
>Take a look at the CASE statement. It is easier than nested IFs.
>
>--
>Terry Dykstra (TeamPS)
>Canadian Forest Oil Ltd.
>Doreen Weekley wrote in message ...
>>Hi Terry:
>>
>>Actually I don't need a lot of nested reports. I was referring more to
>>nesting functions as
>>a simple example: if (a,b,c) where b and c might be another if statement.
>>We often have to parse, manipulate and perform calculations before
>>interpreting the data from the files so
>>it leads to some nesting of functions in the calculated fields that can
get
>>ugly. We try to
>>keep all this on the report, instead of db, side to make it easier for the
>>user to understand.
>>To answer your question about how may computed fields, we may use 15 - 32
>>per report. Probably half of those are used only because these reports
>have
>>to act as templates and since I have not been successful getting alias
>names
>>to work w/multiple tables we use a computed field in place of the column
>>just so it doesn't drop off the report when the table names change. The
>>other half are the result of the ugly calculations/manipulations that are
>>required by the data.
>>
>>Tks for your help
>>Doreen
>>
>>
>>Terry Dykstra wrote in message <5VP$Q6xk#GA.322@forums.sybase.com>...
>>>As far as I know, there are no hardcoded limits. Generally speaking you
>>>will be able to do more under NT, since it has better memory management
>>than
>>>W95. If I find out more, I'll let you know.
>>>Out of curiosity, how many computed fields and / or nested reports do you
>>>have?
>>>
>>>--
>>>Terry Dykstra (TeamPS)
>>>Canadian Forest Oil Ltd.
>>>Doreen Weekley wrote in message ...
>>>>I think I read a response that indicated there was a fixed number of
>>>>allowable
>>>>computed fields in a report. I use a lot of them on some reports and
>have
>>>>noticed some strange behavior and now wonder if I'm exceeding the limit
>in
>>>>these cases. For version 6.5 what is the allowable number? I'm sure
>that
>>>>complexity comes into play as it will affect resources but if there are
>>>>other guidelines that are known, like limits to nesting, would you
please
>>>>point me to where I might find those.
>>>>
>>>>Tks
>>>>Doreen
>>>>
>>>>
>>>
>>>
>>
>>
>
>