If you have need of a subroutine to make a complex
conversion, why not just connect a subroutine record to the
AI. I realize that this adds a record.
Also, the LINR field is an enum. Having it be an enum for
anything it finds and an arbitrary string if it is not
located, is not supported. When we connect to CA, the field
primatives cannot be mixed.
Also - you could make a breakpoint table out of the
algorithm. I've done this for log just for efficiency sake -
it's pretty straight forward.
To recap there are two solutions:
1) link it to a subroutine record
2) make a new breakpoint table for it
Bob
- Replies:
- Re: Apropos making fields configurable Andrew Johnson
- References:
- Re: Apropos making fields configurable Benjamin Franksen
- Navigate by Date:
- Prev:
Re: Apropos making fields configurable Benjamin Franksen
- Next:
scaler record: int -> float Tim Mooney
- Index:
1994
1995
1996
1997
1998
1999
2000
<2001>
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
Re: Apropos making fields configurable Benjamin Franksen
- Next:
Re: Apropos making fields configurable Andrew Johnson
- Index:
1994
1995
1996
1997
1998
1999
2000
<2001>
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
|