>>Hi. my company asked me to try "see4fp" an alternative to Blat. (Blat was leaving off too many attachments).
>>
>>I don't understand the #include portion of directions (below)
>>
>>Instructions:
>>* NOTES:
>>* (1) It is HIGHLY recommended that all INCLUDE statements be replaced by their contents.
>>* For example, delete "#INCLUDE KEYCODE.FOX" and then add "#define SEE_KEY_CODE 0".
>>
>>Subect #Include:
>>

#INCLUDE KEYCODE.FOX
>>#INCLUDE SEE32CON.FOX

>>
>>Only code that matches:
>>

Kode = seeAttach(1, SEE_KEY_CODE)

>>
>>Q: what do I do with the #include lines AND what do I put in the Kode code(above)?
>>
>>Thanks, Randy
>
>
>Sorry I can't answer your question but that's disappointing to hear about Blat. Are you positive the left-off attachments weren't due to a coding bug? Not being accuusatory -- we all have them. I wrote a program that distributed reports by email using Blat and it worked for months without anyone saying they didn't get their report.

I agree (and it's very rare for me to agree with Mike B. :p). I've used BLAT for email in many projects over the years and have been absolutely impressed by it's reliability.

Are you sure you're not having attachments stripped off at the mail server or client end?