Mark,
First, there's only one # sign, it's C#, and it's ASP.Net, not ASP (ASP
was the classic pre-.net stuff). We know what you mean, in other circles
this might cause problems. <G>
Now, on to your questions...
1) Yes, ignoring things like grasshopper and c#->java byte code
converters, it runs on a windows box
2) Yes, you need some connection. JDBC isn't really an option since it's
for java. If you're looking to treat the 400 like a database than what
you want it the Client Access .Net data driver, it's in the client
access setup right next to odbc and oledb. Alternatively you could
implement some sort of custom messaging setup, either over sockets, or
MQ, or web-services, etc. But I'd start w/a simple data connection.
3) The actual reads and updates can come from SQL in C#. The simplest is
to allow reads and updates from the sql in C# and be done, the most
secure is to have the sql in the C# be nothing but stored proc calls for
both reads and updates, and have the stored procs (RPG programs) on the
System i do the actual data manipulation. Somewhere in the middle is
probably the best, doing reads via SQL and updates via stored procs. Of
course, if you did go w/some sort of messaging setup (see #2) then there
would be no SQL in the c#. However, I find it can be a pain if you can't
write the sql in c#. There are times that it's just simpler to write the
sql to join 5 tables, add a couple or where options and set an order by.
:)
-Walden
--
Walden H Leverich III
Tech Software
(516) 627-3800 x3051
WaldenL@xxxxxxxxxxxxxxx
http://www.TechSoftInc.com
Quiquid latine dictum sit altum viditur.
(Whatever is said in Latin seems profound.)
midrange.com
