ADO.Net can do SQL access, remote commands, stored procedures and program calls.
We also use our .Net-ified version of JT400 for IFS access, data queues, data areas, record level access, etc.
As Maurice says: "ADO.Net can do anything. Except the dishes" :-)
JT400 cleans up and does the dishes :-)
Regards,
Richard Schoen
RJS Software Systems Inc.
Where Information Meets Innovation
Document Management, Workflow, Report Delivery, Forms and Business Intelligence
Email: richard@xxxxxxxxxxxxxxx
Web Site:
http://www.rjssoftware.com
Tel: (952) 736-5800
Fax: (952) 736-5801
Toll Free: (888) RJSSOFT
------------------------------
message: 7
date: Thu, 9 Aug 2012 11:47:11 -0700 (PDT)
from: Nathan Andelin <nandelin@xxxxxxxxx>
subject: Re: [WEB400] XMLSERVICE with .Net
From: Richard Schoen
You're so last week :-)
True, it's taking me some time to come up to speed. I had to go read XMLSERVICE articles by Brian, Alan, and Erwin Early.
Of course you are going over QZDSAOINIT, so what's the point of
XMLSERVICE over the QZDSAOINIT transport when the various drivers can
already call stored procedures ?
Did you get my question about XMLSERVICE magic? Evoking WRKSYSVAL? Returning a list of system values to the client? Can you do that with ADO .Net?
-Nathan.
------------------------------
message: 8
date: Thu, 9 Aug 2012 20:05:18 +0100
from: "Maurice O'Prey" <Maurice.Oprey@xxxxxxxxx>
subject: Re: [WEB400] XMLSERVICE with .Net
Nathan
Returning a list of system values to the client? Can you do that with
ADO
.Net?
You can do ANYTHING with ADO.NET!
- Maurice
As an Amazon Associate we earn from qualifying purchases.