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
Microsoft VBScript runtime error '800a0005' while using MID
Eclipse and Tomcat: HTTP Status 404
Hyper-V R2 virtual machine storage on ISCSI SAN affecting live migration
4 functions and call one randomly on click
Want to run script when a file is put in a folder
Select menu to change MySQL Query
ASP.Net Wizard control
A substitute for Terminal Server running under 2003. Any 3rd party tool, having basic features of TS?
proxy server
How could insert crystal report inside a form or maximum it to be full screen