Sim Zacks <sim@xxxxxxxxxxxxxx> writes: > The reason why the client application would have to wait is because > the front-end is written in MSAccess. While Windows supports multi > threading, Access does not support multi threading. > (Multi threading allows background processing, IYDK) Well, you *clearly* need to have some sort of "daemon" running in order to do this. I expect it will in effect be a LISTEN process that waits for clients to submit NOTIFY requests. Even if you don't actually choose to use NOTIFY/LISTEN, per se, you'll doubtless wind up creating an ad hoc, informally-specified implementation of part of it... -- let name="cbbrowne" and tld="ntlug.org" in name ^ "@" ^ tld;; http://www.ntlug.org/~cbbrowne/unix.html "Any sufficiently complicated C or Fortran program contains an ad hoc informally-specified bug-ridden slow implementation of half of Common Lisp." -- Philip Greenspun
