Microsoft
Software
Hardware
Network
Question : ASP Connection String vs. Database Access DLL
I am working with our web developer to find a way to connect to our AS/400 from ASP.NET running on Server 2003. My first inclination is to create a database DLL that connects to the AS/400 and returns various data elements from Stored Procedures. I can hard code a connection string in the DLL that I create with C# to access the AS/400 database. The access to our AS/400 can be limited to calling only a select group of stored procedures. The ASP.NET application would simply utilize the DLL to connect to the AS/400.
We could also store the connection string in the Web.Config file on the ASP server. I understand that if our server gets hacked, that connection string could be viewed.
Is there a best practice for this kind of connection? Anybody doing ASP connecting to the AS/400 (System-i)?
Answer : ASP Connection String vs. Database Access DLL
have you tried attaching the batch as a startup/shutdown script in GPO? (I'm thinking at shutdown may be better- that way there isn't issues with users are waiting for install).
Random Solutions
A perl spreadsheet problem--reading from a specific tab
How can I have MS project on my computer?
Maintain the some files on 2 machines in real time
2 exchange accounts on a droid incredable
Outlook 2002 send receive fail
Outlook follow up folder in favourites
asp.net
SqlDataSource, Gridview and Update & Delete process
SBS 2008 BPA - User Account QBDataServiceUser17
Help with MX Records Idiots guide please!