Our programmers are writing web applications that connect to SQL databases. We want it so that they can be moved to different IIS or SQL servers as easily as possible. I thought that using either system of file DSN's would be the way to go, but our programmers say: " DSN is "hard wired" on the machine or server. DSN-less connections mean I can access the database from any computer, anywhere. The connection string is within the code, in an include file. The config files will be used to put in database info, file locations and other essential information so the info can be modified if required." As a network administrator, I want to be able to move these apps without any knowledge of the app itself or the code it was written in. Can somebody please tell me what best practice is when writing these apps? Thanks, R ******************************************************** This Weeks Sponsor Emergent Online ThinCity Conference Join us at ThinCity 2004: The 1st Annual Emergent OnLine Technology Conference http://www.ThinCity.com ********************************************************** Useful Thin Client Computing Links are available at: http://thin.net/links.cfm *********************************************************** For Archives, to Unsubscribe, Subscribe or set Digest or Vacation mode use the below link: http://thin.net/citrixlist.cfm