RB Error Help

Yahoo Archive
1
Thanks Gordon. That was exactly it.
Was sorting on a desc field that usually works. Extra long data was added
this month.
Thanks again.

Jim

-----Original Message-----
From: Gordon Schindell [mailto:gordons@...]
Sent: Monday, June 30, 2003 9:31 AM
To: 'vantage@yahoogroups.com'
Subject: RE: [Vantage] RB Error Help

When I see this error it's because I'm trying to sort on a field that
contains a value that is too long. For instance, when I try to sort all
parts by description, and someone has created a part with a couple of
paragraphs of text for a description. RB chokes on this.

To work around:

(1) create a quick report that shows what the offending value is:
Calculated Field: DescriptionLength = LENGTH(PartDescription), Filter:
DescriptionLength > 100

(2) Even better: Instead of sorting on the field which could potentially be
too long, replace the field in your report with a calculated field called
ShortPartDesc, Expression: SUBSTRING(PartDescripton,1,50). This calculation
only takes the first 50 characters of the long field and sorts on that.

Gord Schindell
Network Admininstrator
Almac Machine Works.

-----Original Message-----
From: Moore, Jim (Anniston) [mailto:jmoore@...-ots.com]
Sent: Monday, June 30, 2003 8:05 AM
To: 'vantage@yahoogroups.com'
Subject: [Vantage] RB Error Help


I have a RB report that has run for a while now that started giving the user
this error. "Database request failed. Database error is: ** Index value is
too long. (141)

This report is a Monthly Shipping Report and the filter that seems to be the
problem is Shiphead.ShipDate IN-RANGE 05/26/2003, 06/26/2003
An earlier date range worked fine. (The one in 2001 that was there when the
report was created.
Any idea what has happened. Nothing has changed on this report in a long
time.

Thanks,
Jim Moore
GD-OTS


[Non-text portions of this message have been removed]



Useful links for the Yahoo!Groups Vantage Board are: ( Note: You must have
already linked your email address to a yahoo id to enable access. )
(1) To access the Files Section of our Yahoo!Group for Report Builder and
Crystal Reports and other 'goodies', please goto:
http://groups.yahoo.com/group/vantage/files/.
(2) To search through old msg's goto:
http://groups.yahoo.com/group/vantage/messages
(3) To view links to Vendors that provide Vantage services goto:
http://groups.yahoo.com/group/vantage/links

Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/



Useful links for the Yahoo!Groups Vantage Board are: ( Note: You must have
already linked your email address to a yahoo id to enable access. )
(1) To access the Files Section of our Yahoo!Group for Report Builder and
Crystal Reports and other 'goodies', please goto:
http://groups.yahoo.com/group/vantage/files/.
(2) To search through old msg's goto:
http://groups.yahoo.com/group/vantage/messages
(3) To view links to Vendors that provide Vantage services goto:
http://groups.yahoo.com/group/vantage/links

Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
2
I have a RB report that has run for a while now that started giving the user
this error. "Database request failed. Database error is: ** Index value is
too long. (141)

This report is a Monthly Shipping Report and the filter that seems to be the
problem is Shiphead.ShipDate IN-RANGE 05/26/2003, 06/26/2003
An earlier date range worked fine. (The one in 2001 that was there when the
report was created.
Any idea what has happened. Nothing has changed on this report in a long
time.

Thanks,
Jim Moore
GD-OTS


[Non-text portions of this message have been removed]
3
When I see this error it's because I'm trying to sort on a field that
contains a value that is too long. For instance, when I try to sort all
parts by description, and someone has created a part with a couple of
paragraphs of text for a description. RB chokes on this.

To work around:

(1) create a quick report that shows what the offending value is:
Calculated Field: DescriptionLength = LENGTH(PartDescription), Filter:
DescriptionLength > 100

(2) Even better: Instead of sorting on the field which could potentially be
too long, replace the field in your report with a calculated field called
ShortPartDesc, Expression: SUBSTRING(PartDescripton,1,50). This calculation
only takes the first 50 characters of the long field and sorts on that.

Gord Schindell
Network Admininstrator
Almac Machine Works.

-----Original Message-----
From: Moore, Jim (Anniston) [mailto:jmoore@...-ots.com]
Sent: Monday, June 30, 2003 8:05 AM
To: 'vantage@yahoogroups.com'
Subject: [Vantage] RB Error Help


I have a RB report that has run for a while now that started giving the user
this error. "Database request failed. Database error is: ** Index value is
too long. (141)

This report is a Monthly Shipping Report and the filter that seems to be the
problem is Shiphead.ShipDate IN-RANGE 05/26/2003, 06/26/2003
An earlier date range worked fine. (The one in 2001 that was there when the
report was created.
Any idea what has happened. Nothing has changed on this report in a long
time.

Thanks,
Jim Moore
GD-OTS


[Non-text portions of this message have been removed]



Useful links for the Yahoo!Groups Vantage Board are: ( Note: You must have
already linked your email address to a yahoo id to enable access. )
(1) To access the Files Section of our Yahoo!Group for Report Builder and
Crystal Reports and other 'goodies', please goto:
http://groups.yahoo.com/group/vantage/files/.
(2) To search through old msg's goto:
http://groups.yahoo.com/group/vantage/messages
(3) To view links to Vendors that provide Vantage services goto:
http://groups.yahoo.com/group/vantage/links

Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/