To my knowledge the actual structure and it's sub-structure is of no importance 
at all - you only pass a memory pointer. You use the Length field to control 
how many bytes to use of the key.


/Joakim

        -----Ursprungligt meddelande-----
        Från: c400-l-bounces+joakim.svensson=capgemini.com@xxxxxxxxxxxx genom 
Adam Walker
        Skickat: må 2005-01-10 11:58
        Till: c400-l@xxxxxxxxxxxx
        Kopia:
        Ämne: RE: [C400-L] using _Rreadk with a partial key - any examples?



        I tried setting the other fields to blank or 0, but no joy.  So i've 
removed those fields from the struct and just kept the seq.  The key length is 
set to the struct size.  this approach seems to work well.

        thanks for your help guys.

        solution:

        typedef struct {
         decimal(7,0) seq;   
         //char sCus[6];
         //char sCLC[3];
         //char cPrime;
        } SXKey;

        ....
        ....

            char* pKeyBuffer = malloc(sizeof(SXKey));
            SXKey* pKey = (SXKey*) pKeyBuffer;
            int nKeyLength = sizeof(SXKey);
            pKey->seq = 28;

        ....
        ....

            pFeedback = _Rreadk(pFile, 
pRecBuffer,nRecLength,__KEY_EQ,pKeyBuffer,nKeyLength);



This message contains information that may be privileged or confidential and is 
the property of the Capgemini Group. It is intended only for the person to whom 
it is addressed. If you are not the intended recipient,  you are not authorized 
to read, print, retain, copy, disseminate,  distribute, or use this message or 
any part thereof. If you receive this  message in error, please notify the 
sender immediately and delete all  copies of this message.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].