Well then, how's about spelling out the word INTEGER in your parameters?

again, good luck


>Good guess Jim,
>
>But I already attempted alias "foobar" with the same result. No cigar. Thanks for taking a look at this, it has me befulddled (sic).
>
>Thanks
>
>Glenn
>
>
>
>>Glenn,
>>
>>Could there be a same-named FUNCTION in your executing code and that uses fewer parameters in its execution?
>>
>>Obviously a pure SWAG.
>>
>>good luck
>>
>>
>>>Thanks Mark,
>>>
>>>Been there done that! It started that way, and I spaced it according to the VFP documentation. Neither way works.. I appreciate you looking at it though... sorta like Extreme debugging.
>>>
>>>Glenn
>>>
>>>>Remove the space between @ and cRecord.
>>>>
>>>>>I have been trying to implement a set of API function calls. All the other calls work just fine but this one fires VFP error #1230 (Too many arguments).
>>>>>

>>>>>declare integer ls_getRecord in (lcDll) ;
>>>>>	long lsHndle,long nRecno,int nFmtCode,string @ cRecord,int nRecordLength
>>>>>
>>>>>NlEN = ls_getRecord(lnStru,i,6,@cRecord,nBufflen)
>>>>>

>>>>>
>>>>>the same call in C## is

>>>>>DLLIMP int  CALLX ls_getRecord(char *h,
>>>>>		long recNum /* 1 origin physical rec# */,
>>>>>		int fmtCode, char *recbuf, int recbuflen);
>>>>>
>>>>>nRv = ls_getRecord(h,rn,rqCode,sFmtBuf,sFmtBufLen);
>>>>>

>>>>>
>>>>>Does anyone have any suggestions, recommendations, straight jackets?
>>>>>
>>>>>Glenn