PE>> If you insist on running crappy software that can't handle
PE>> messages of 35k in size, well what can I say except
PE>> WHERE'S YER BLOODY CAPS KEY?
KR> well, if thats all you can say, you may as well shut up.
Ok.
PE>> What mailprocessor does ppoint use actually, is it squish? If
PE>> so, get with the times, man! 1.10 has already hit the streets.
KR> it uses it's own, the only externals are the comms prog (bink), the
KR> editor (ezequote), and the spellchecker (if you care to use one).
I thought it just said that it was truncated, not blow up?
KR> no thanks, i have been mulling over the idea of writing a point all of
KR> my very own. it would be a windows prog (what else would anyone want to
KR> write for?), and use a standard database such as the paradox engine for
KR> the messagebase. anyone could then write extensions or additions using
KR> the standard available tools. i suppose that i could use access as it is
KR> designed to integrate into the environment (and we have a developers kit
KR> at work).it all really depends on how quickly i can climb the learning
KR> curve (and how much time i waste on e-mail (-8 )
Sounds great. Why don't you use Microsoft Access (which has
SQL - we have it at work). I don't know what the technicalities
involved in getting a C program to call the SQL are though.
Why not knock up something bare-bones and give it to me to test
out? I can put up with a lot of deficiencies. BFN. Paul.
@EOT:
--- Mksmsg
* Origin: none (3:711/934.9)
|