@dbcommand odbc stopped working!

Please help - this is really weird!Yesterday I developed a form with some computed text that retrieved data from our corporate SQL 2000 database using @dbcommand with ODBC.

These all worked ok when I refreshed the form.

This morning, nothing - they not only don’t retrieve the data, they don’t seem to be doing anything at all (i.e. not even failing, just not activating).

Nothing has changed - no upgrades to client or server, or the odbc dsn, or SQL server.

They had the form

@Dbcommand(“ODBC”:“NoCache”;“odbc_dsn_name”;“login”;“password”;“select surname from people where customer_reference = 123456”:“fail”)

Things I have tried :

  1. doing the same in another database in case it is a database setting. Same result (or lack of) in other database

  2. Restarting Domino (even though the form is on the client and this shouldn’t matter)

  3. Changing the sql statement to be invalid (adding random characters) - this should force an error, but still saw nothing, which suggests the @dbcommand isn’t firing at all

  4. Trying it on another workstation in case it is a setting - still no luck

  5. Checked the ODBC is still a valid dsn by successfully executing the same sql as a data retrieval in Excel.

  6. tried @dbcolumn instead of @dbcommand - still no output

Update

I have just tried with a ‘computed for display’ field instead of computed text, and it works! However, I am worried this will also stop working - or is there some essential reason why it is unreliable on a computed text item?

Any help / explanations welcome!

Subject: Even weirder!!

Thinking I would change all the computed texts to ‘computed for display’ fields, I add the first cfd field and tested it - now ALL the computed text fields work again! WTF?

Can anyone explain this - is there some kind of low level caching for computed text?

Regards