What we do is to set the database to <@var system$database> (for the deployment value), as well as providing dynamic variables for database name, password and user.

Then we add lines to the witango.ini file in each server that correspond to the type of database (including lines for database name, host, user, and password) - so in your case, to development, add

database=ODBC

and add to your production server

database=JDBC

works like a charm

If you don't like the idea of adding these to your witango.ini file, you can always have a taf that starts up with the server that assigns the variables in the scope you want to use.

On Jul 8, 2004, at 11:36 AM, John McGowan wrote:

Anybody know if this is possible.

I have a W5 running on Linux and we're using a JDBC driver to talk to MSSQL. however in the development environment we're still using ODBC to talk to the DB server. So currently when I have a TAF or TCF that I want to run on the Linux server I do a search and replace in the XML to replace ODBC with JDBC. and that allows me to run the code with no problem assuming I've setup the JDBC datasource.

Here's my question. Since I have NO intention of using ODBC on the Linux W5 server is there a way that I can configure the witango server to use JDBC instead of ODBC even if it sees ODBC. either on a server wide basis or on a per DSN basis. This would save me the step of doing the search and replace every time I push the files to the server.

/John

_______________________________________________________________________ _
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf



________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf

Reply via email to