>I've had this happen as well. Generally the server runs OK, but when deadlocks occur and I track down the last T-SQL command for the deadlocked process, it is a simple SELECT statement. The only consistency I have found is that the only time I have seen this happen the DATE() function has been part of the SQL statement. I am running SQL 7.0 SP3 on this particular server by the way. The original developer told me that he has never had this happen to him in 2 years and we are running identical enviroments. My only guess at this point is some sort of hardware failure or software conflict rather then the transactions themselves.

Now when you say DATE(), you mean the VFP DATE() function? We are running into this with queries against our SQL tables, (using both the ODBC and OLEDB drivers for SQL Server) but we're certainly not passing the DATE() function, just the return value, usually converted to a string.