> I am under some restrictions as to which version of James I am
> sanctioned to run. I am aware of the tremendous amount of work
> has been done in getting to 2.1...
> Until then I am running 20a3 and have found issues that I believed
> have not been addressed
> therefore my arrogance and chest pounding about the apparently faulty
> operation of a severed db connection.
Well, maybe table pounding, but that's about it. As far as Danny and I can
tell, the problem doesn't exist in the current code. But you can't run the
fixed code, so what would you have us do? Other than get v2.1 officially
released. :-)
As I said, in the future I hope that we can fairly rapidly get out new
release versions in response to defects.
--- Noel
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
