Unreliable connection between ODBC content tables and SQL Server 7 databases causes data to "dissapear".

[Stephen Steele]

ODBC connections to a SQL Server 7 database are unreliable. ODBC content
tables based on SQL queries seem to lose contact with ADO and hence the
database on the server. Furthermore, this kind of break in communication
with the server undermines recordsets which draw from the root queries and
any contracts which are applied to those recordsets. This error does not
appear to have a predictable MO, one table may be "dropped" while others in
the same site are sustained.

According to Macromedia Support there is no solution to the above problem. I
have Installed SP3 for SQL 7.0 - which didnt help.

I have 1 particular query that I can not even create a content table for,
even though the query tests OK

the Workaround suggested of using Access for development would be a lot of
work (I use GETDATE() which doesnt work in access)

Has anybody else come across this problem and found a solution ?

Thanks in advance

Stephen Steele

[BrynnX]

In your particular situation, could you use a server side script to get date
value...maybe for a hidden field...then just have that "text" value goto the
database.

"Stephen Steele" <st...@ssteele.freeserve.co.uk> wrote in message
news:91t5ru$hub$1...@misc.macromedia.com...

[mailxyz]

Common problem. Might have been fixed in v4, had there been a v4...

Disconnecting and reconnecting (via the content table) is the only
workaround.

--
r.andersen
remove xyz