[EMAIL PROTECTED] wrote:
Hi Michael,
Sorry, I sent my previous reply directly to you instead of to the
list.
thanks for the hint, I already looked into the code and - by the
way - I find it very well structured. However, one question is
left. There´s always spoken about using async
Arno,
if I'd do it the way you suggest (do it async, fetching the next record
in OnRequestDone and start over sending), may I use screen output from
there, including .ProcessMessages? I know that a good application should
display information based on a timer or such, i.e. re-displaying all
Michael Kochendoerfer wrote:
Arno,
if I'd do it the way you suggest (do it async, fetching the next
record
in OnRequestDone and start over sending), may I use screen output from
there,
Yes, of course, take a look at the demo.
including .ProcessMessages?
No no, why would you need
Hello bevan,
Is it text file or binary file ?
If text file be sure to set binary mode, if not all #13#10 may be
converted into #10 if destination is Unix system so each text line
will loose 1 byte.
regards.
bacn Sorry, I sent my previous reply directly to you instead of to the list.
Dod wrote:
Hello bevan,
Is it text file or binary file ?
If text file be sure to set binary mode,
In SMTP??
---
Arno Garrels [TeamICS]
http://www.overbyte.be/eng/overbyte/teamics.html
if not all #13#10 may be
converted into #10 if destination is Unix system so each text line
On Jan 13, 2007, at 04:50, Dod wrote:
Hello bevan,
Is it text file or binary file ?
If text file be sure to set binary mode, if not all #13#10 may be
converted into #10 if destination is Unix system so each text line
will loose 1 byte.
In SMTP, you encode the file using MIME
Hi Michael,
Sorry, I sent my previous reply directly to you instead of to the list.
thanks for the hint, I already looked into the code and - by the way - I
find it very well structured. However, one question is left. There´s
always spoken about using async components, but in my special case