Not sure if some of this will work or be acceptable performance wise but just to toss a few things out...
1. Instead of Integer maybe a different function would work...like convert to string with an integer type mask of ">>>>>>" and then back to a number with the NUMERIC function.
2. Very slim chance but sometimes running things through an aggregate works (like Min or Max with level set at the level you need to link at). More often than not though RB chokes really bad when involving aggregates in links.
3. Worst case (but will work)....link only via company in each table and select by filtering. Performance will take a steep hit but if the other factors make this a smaller record complex it can be acceptable. If you are looking at thousands of records though it will really drag. Optimize the linking to use index fields in other tables as much as possible ahead of the BOLNumber test as well as other index related tests ahead of it to reduce the size of the record complex before it does that one - things such as limiting date range work well.
-Todd C.
-----Original Message-----
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com]On Behalf Of Keith Mailloux
Sent: Friday, October 13, 2006 2:32 PM
To: vantage@yahoogroups.com
Subject: [Vantage] RB Index problem
I am trying to join a table to the BOLHead file. The originating table
(APHead) has the BOL number stored in a numeric VB field (Number01).
When I try to build the join I get an error telling me "Use INTEGER
function to compare integer index-field and decimal (46)". So I create a
calculated field using the INTEGER function using the master table VB
field (Number01). Now when I go to build the join and look under the
calculated field folder the calculated field is not available to select.
I remember someone once having a cheat for this (I think). Any thoughts?
Thanks
Keith
---------------------------------
This e-mail and any attachments may contain confidential and
privileged information. If you are not the intended recipient,
please notify the sender immediately by return e-mail, delete this
e-mail and destroy any copies. Any dissemination or use of this
information by a person other than the intended recipient is
unauthorized and may be illegal.
[Non-text portions of this message have been removed]
[Non-text portions of this message have been removed]
1. Instead of Integer maybe a different function would work...like convert to string with an integer type mask of ">>>>>>" and then back to a number with the NUMERIC function.
2. Very slim chance but sometimes running things through an aggregate works (like Min or Max with level set at the level you need to link at). More often than not though RB chokes really bad when involving aggregates in links.
3. Worst case (but will work)....link only via company in each table and select by filtering. Performance will take a steep hit but if the other factors make this a smaller record complex it can be acceptable. If you are looking at thousands of records though it will really drag. Optimize the linking to use index fields in other tables as much as possible ahead of the BOLNumber test as well as other index related tests ahead of it to reduce the size of the record complex before it does that one - things such as limiting date range work well.
-Todd C.
-----Original Message-----
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com]On Behalf Of Keith Mailloux
Sent: Friday, October 13, 2006 2:32 PM
To: vantage@yahoogroups.com
Subject: [Vantage] RB Index problem
I am trying to join a table to the BOLHead file. The originating table
(APHead) has the BOL number stored in a numeric VB field (Number01).
When I try to build the join I get an error telling me "Use INTEGER
function to compare integer index-field and decimal (46)". So I create a
calculated field using the INTEGER function using the master table VB
field (Number01). Now when I go to build the join and look under the
calculated field folder the calculated field is not available to select.
I remember someone once having a cheat for this (I think). Any thoughts?
Thanks
Keith
---------------------------------
This e-mail and any attachments may contain confidential and
privileged information. If you are not the intended recipient,
please notify the sender immediately by return e-mail, delete this
e-mail and destroy any copies. Any dissemination or use of this
information by a person other than the intended recipient is
unauthorized and may be illegal.
[Non-text portions of this message have been removed]
[Non-text portions of this message have been removed]