As you seem to know you should store the connection strings in the
connection string section of Web.Config and retrieve them using the
configuration manager (I am a little confused as why you are not doing this,
sorry if I misunderstand)
e.g. MyConStr =
And of course you can encrypt them (every good book on .NET has a section
covering this). I don't use Navigator (nor drag and drop) I write all code
manually but you should be able to move the connection strings to the
I use ISO date fields on the iSeries and so far have learned to live with
this (had to write a view little date utilities in .NET to display them in
the correct format but nothing that is too different from what we have all
done in RPG.
Finally I do believe you can set up a DB2/400 database in SQL server as a
linked database but I have never pursued that route as using the IBM .NET
managed data provider to connect directly is straight forward and probably
provides better performance. Google will provide quite a bit of info on this
but its not the way I would go.
From: web400-bounces@xxxxxxxxxxxx [mailto:web400-bounces@xxxxxxxxxxxx] On
Behalf Of Mary Koetting
Sent: 14 April 2008 21:42
Subject: [WEB400] ASP.NET and the iSeries - New Thread
Thank you, Maurice!
I do have all the insert, deletes and updates created in stored
procedures using iseries navigator...but the connection strings (along
with userid's and passwords) are all in the code-behind and I thought
that they should be encrypted in the web.config file...
Another question that I have is about date fields...I have defined the
fields as dates on the iseries but null date fields are a pain when
display/comparing a null field and when compiling the program. Does
everyone use date fields and see their advantage?
To explain my question, I thought I heard or read that you can set a
file on a SQL server that would pull the data from an iseries
file...kind of like a DDM file...one would send the SQL to the SQL
server and it would hook into the iseries and update the data according
to the SQL statement.
Senior Programmer Analyst
Missouri Consolidated Health Care
This mailing list archive is Copyright 1997-2019 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact