OK, this seems more than a bit weird to me (must be Friday afternoon!) ... Our QA guys are testing a new VB.NET application which connects to UV via UVObjects and calls a subroutine that calls a subroutine that writes one record and PHANTOMs off a batch-type job. The VB app was written with a UVObjects Begin Transaction and Commit Transaction wrapped around it. When they looked in the &PH& entry, it was full of 'Verb "<various verbs>" illegal when a transaction is active' error messages.
************************************************************* So it looks like Transaction State persists across a PHANTOM invocation!?!? I'm shocked, horrified, amazed, etc. ************************************************************* Is this a feature or a bug? If a feature, is it documented anywhere? Anyone come across this before? Any suggestions on how to avoid it, other than not putting the web side into Transaction State? The whole point of writing a work-to-do record and PHANTOMing off the worker process was to de-couple the Web and UV parts of the system. Thanks Mike The information contained in this Internet Email message is intended for the addressee only and may contain privileged information, but not necessarily the official views or opinions of the New Zealand Defence Force. If you are not the intended recipient you must not use, disclose, copy or distribute this message or the information in it. If you have received this message in error, please Email or telephone the sender immediately. ------- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
