Hi Dave I noticed that you are using the @@ there are times this can be unreliable, this might be one of those times (ODBC, @@user$odbc, name, password) You might want to try <@var user$odbc encoding="none">
Also, it seems strange that you are using the USER scope for this. This means that if the var timeout hit then there is no value there for odbc so then it might use the next avail connection. Shouldn't this be a domain or application scope? Another question: are you using different users for the different databases? Ben -----Original Message----- From: Dave Machin [mailto:[EMAIL PROTECTED] Sent: Thursday, January 12, 2006 3:35 PM To: [email protected] Cc: [EMAIL PROTECTED] Subject: Witango-Talk: Strange ODBC Problem We're trying to track down a strange database problem We're having a few occurrences where a query seems to executing against the wrong ODBC connection. We're using a variable for our ODBC name in the DataSource. What seems to happen is that sometimes the query executes against the ODBC listed as the development data source instead of the deployment data source (which uses the variable). The set deployment data source checkbox is checked. Then "specify" radio button is selected. Then "same as development" is unchecked and the form filled in (ODBC, @@user$odbc, name, password). This seems to happen very seldom, maybe one or two transactions per day (out of 400 to 500 thousand page requests, each with several database queries in them). The .taf file doesn't have any aberrant "!CST" entries in it. The query in question is a drag-and-drop search action. We're running Witango 5.5.009 on Windows 2000 against MS-SQL database. Anyone have a problem like this? Dave Machin [EMAIL PROTECTED] ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
