Witango-Talk: Revisiting http headers

2008-07-01 Thread WebDude
I understand that when I assign this to the not found file, it works correctly when the actual file does not exist. However, is it possible to get this to work on a no results page? I tried this at the head of a no results page, yet IIS5 logs show it as being found. Any way around this? This is

Re: Witango-Talk: Revisiting http headers

2008-07-01 Thread Scott Cadillac
Hey Dude, Remember, IIS handles the request before Tango does, so technically speaking IIS did find your page, otherwise the TAF would not have executed your code. What counts is that the browser got a 404 response from the server. Hope that helps. Scott, On Jul-1-2008, at 1:21 PM,

Re: Witango-Talk: Revisiting http headers

2008-07-01 Thread D. Richardy
You can change the 404 response into a another document like CLICK HERE or something else... regards Daniel www.softdes.de (my first funy work since 1991) www.protreff.net (my second funy work since 2002) www.zum-henker.com (my third funy work in Saxony since 2008) - Original Message

Re: Witango-Talk: Mac studio errors on odbc connection

2008-07-01 Thread Roland Dumas
What's weird is that I don't have the opportunity to enter my password. As soon as I open a datasource, it gives me an error. I check my ODBC settings and the myodbc utility says the connection is good. Something in witango studio is dented. Looking for where witango studio stores its

Re: Witango-Talk: Mac studio errors on odbc connection

2008-07-01 Thread Roland Dumas
found the right prefs file to nuke and the problem was cured. On Jul 1, 2008, at 10:20 PM, Roland Dumas wrote: What's weird is that I don't have the opportunity to enter my password. As soon as I open a datasource, it gives me an error. I check my ODBC settings and the myodbc utility says

Re: Witango-Talk: Mac studio errors on odbc connection

2008-07-01 Thread Robert Garcia
You don't need to nuke prefs. This is from memory, so right click on the datasource in witango and hit properties. Then you uncheck the SAVE password box, this will force it to ask you next time. This just is something that happens frequently in the mac studio. Maybe it will be fixed