-- 

Robert Garcia
President - BigHead Technology
VP Application Development - eventpix.com
13653 West Park Dr
Magalia, Ca 95954
ph: 530.645.4040 x222 fax: 530.645.4040

On Jan 25, 2006, at 2:08 PM, Dave Machin wrote:

One(!) question - the two queries that were done sequentially, and you

separated out, were they identicle queries except for the dsn?




Yes, actually, there USED to be 4 in a row. Now, there are 2 in a row, for each dsn, 1 for different tables as shown. The db3 actions above, I specify a different deployment dsn, the non db3, I leave to same as development. I could have used a var here, I just did this quickly to debug, but it helped solve the issue, so I left it alone.


One suspision I've been having is that something bad happens if we issue the

exact same query twice in a row, either to the same dsn (which would be

redundent) or to a different dsn.


Oh, I lied, one more question - how were you detecting the tcp/ip

disconnects?  We're on Windows, is that an ODBC debug thing?


I actually got a witango error, saying the database was not reachable via tcp/ip. I don't remember the exact error, would have to look it up.

Reply via email to