Hi All, We are moving towards "Microsoft BizTalk Server" as the standard 'glue' between our disparate systems. [Yes, I know that the U2 products now talk to IBM's MQ-series products natively, but we don't have any IBM infrastructure, we're mostly an MS shop. Another big advantage is that BizTalk provides as standard a link to and from our SAP Enterprise R/3 ERP system, which is otherwise, umm, not quite the easiest thing to talk to. ;-) ]
At the moment, I imagine we will write some VB.Net components using UniObjects to talk to UniBasic routines embodying the business logic and doing the actual UV database updates. Is this a great / good / adequate / poor / really awful idea? Anyone 'been there, done that, still got the scars'? Thanks Mike ---------------------------------------------- Mike Henderson Senior Analyst / Programmer, Corporate Applications Communications & Information Systems Branch NZ Defence Force 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 [EMAIL PROTECTED] http://www.oliver.com/mailman/listinfo/u2-users
