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
Server Local Group to Domain Local Group
If attribut is ... then do this
How do I set a form to open when Access 2007 and/or 2010 opens a data base?
Default VLAN issues on a Powerconnect 6200
VBA Error Handler when excel sheet does not exist
cfapplication sessionTimeout question
want to align the iframe to the right of the td
windows cannot access the specified drive, path, or file. You may not have the appropriate permissions to access the item
site review
move from 2008 to R2 (compared to 2008 from 2005)