Looks like 65535 is the max value for nFileEnd to be.... must be maxing out the string variable sFileData...

Guess I'll have to wrap the call with a check for the value of nFileEnd.

Thanks!

>The error message 'Function argument, type, or count is invalid' is one that I love. Does not tell you much at all. What I have found is that I could not trust my error handler about 50% of the time to give me the correct line it is happening on. So what I do is if the line it gives me does not make sense at to the error, I proceed to back up a few lines to see if the problem is there. I know this is not much help, but you might want to look at code just previous to the line reported.
>
>
>>This code is part of a email package that sends out emails automatically to our salesreps - and has worked great in other systems here...
>>
>>but..
>>
>>the latest one I released to production just blew up when run for the 1st time (at least that I've been told).
>>
>>Here is the code..
>>
>>

>>*****************************
>>IF pbMailSent
>>	*-- Read Log File
>>	nFileHandle = FOPEN(sLogFile, 10)
>>	nFileEnd = FSEEK(nFileHandle, 0, 2)
>>	nFileBeg = FSEEK(nFileHandle, 0)
>>	IF nFileEnd > 0
>>--->Bad Line--->  sFileData = FREAD(nFileHandle, nFileEnd)
>>	ELSE
>>		sFileData = ''
>>	ENDIF
>>	nFileClose = FCLOSE(nFileHandle)
>>		
>>	DO LogMail WITH sFileData, .T.
>> 	*=MESSAGEBOX('Email sent successfully!' , 48, 'RSVP')
>>WAIT WINDOW 'Email sent successfully to ' + SUBSTR(psMailTo,2,LEN(psMailTo)-2) NOWAIT
>>Else
>>	WAIT CLEAR
>>  =MESSAGEBOX('Email not sent.  There was an error', 48, 'RSVP')
>>ENDIF
>>*********************************
>>

>>
>>In the bad line above I get the error message 'Function argument, type, or count is invalid'.
>>
>>These are the values
>>
>>nfileHandle = 49
>>nfileEnd    = 81500
>>
>>They are numeric....
>>
>>so any ideas???
>>
>>Thanks a heap!
>>Tommy

Tommy Tillman A+ NetWork+ MCP