nkuebelbeck and Craig,
I actually put together a XMLInterop process (with some examples from nkuebelbeck - thanks again). I was able to create a windows service to act as a listener where our third party app could use the service to dispatch the actual XML call. Had to do it this way because the app is 64bit and the edwards install is 32bit... made for a few creative weeks. Anyway, that was all working but the roundtrip for the transactions was VERY lengthy. The box making the call was located across the US from the Edwards install. We started toying with SQL inserts as a way to avoid some of the overhead (since XML has to establish a connection, handshake, post the file, etc.). SQL turned out to be much quicker (since JDBC can be established then direct inserts until transactions are complete) and then come back only when more interaction is required. Anyway, I thought about what you both suggested - basically allow for the SQL inserts to continue and basically have the XML Interop call send a message just to notify JDE that there was some activity performed and that it should go through and process whatever it finds in that table. The only concern I have, and the reason i've avoided doing it, is due to the increase in transaction time. If the volume weren't high and this was a one-off process, i'd go for it, but the frequency of usage will be very high and I think over time the compounding of that transaction time would cause issues.