>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. Well DOBC is pretty much the abstraction layer you want. Something, somewhere, has to know the name of the database server that has the data you want, right? ODBC is what, among other things, provides a layer of abstraction between an application and a database provider. If your application has a catchy name like APP, then make a ODBC connection called APP. Tell your programmers that all database access should be made through a DSN connection you are going to call "APP". Configure the APP DSN to point to whatever database you want. When the data moves to another DB server, change the server name in the APP DSN. The application itself won't know anything has changed and of course no change to the application would be required. If, on the other hand, your app moves to new IIS server, just create a DSN on that server called APP. The SQL server won't know that anything has changed. If that's not what you are after, please clarify. ******************************************************** 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