PH710G

[alex ling]

---EDISR@dteenergy.com wrote:
>
> Hi Alex 
>  
> Why don't you make you define item a short binary rather than
modifying a 
> table attribute?  It seems to me that if your table definition is a
short 
> binary type and you are going to match this type with a variable,
then the 
> variable shouldn't be able to contain a larger value and the match
value 
> anyway (IMHO). 
>  

Sorry, the last example was too simple and misleading. The actual case
has another REQUEST before REQUEST A, where DEAL-REF is a LONG BINARY
in Interbase.

REQUEST BEFORE-A
  etc
  DEFINE X NUM*6 = DEAL-REF OF TABLE-DEAL
  etc
  SUBFILE SS INCLUDE X, etc
REQUEST A
  etc
  DEFINE X NUM*6 = ITEM-X OF TABLE-X
  etc
  SUBFILE SS APPEND INCLUDE X, etc
REQUEST B
  ACCESS *SS LINK X TO ITEM-X OF TABLE-X
  etc

(where ITEM-X is a SHORT BINARY Interbase field)

The fact is the code is working fine in prior versions of PH and above
example is just a simple case to illustrate the problem. We have tons
of complicated QTP and QUIZ financial programs and I don't want to
have to  re-code them.

Thanks for your suggestion. Appreciated.

Regards,
A Ling.

_________________________________________________________
DO YOU YAHOO!?
Get your free @yahoo.com address at http://mail.yahoo.com

= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
Subscribe: "subscribe powerh-l" in message body to majordomo@lists.swau.edu
Unsubscribe: "unsubscribe powerh-l" in message to majordomo@lists.swau.edu
powerh-l@lists.swau.edu is gatewayed one-way to bit.listserv.powerh-l
This list is closed, thus to post to the list, you must be a subscriber.