A few days I ago I posted a request for info about using VFPODBC.DLL (via ADO) from an ASP application. Uh... there weren't many replies.

Anyway, one of the questions I asked about was collision management... how the ODBC driver handles it. Well, I think I can share the answer to that one: It's up to you. You can send a SET REPROCESS command to the ODBC driver by using the Execute method of the ADO connection object. If you don't change the default for REPROCESS, an INSERT or UPDATE command will fail after a second or so if the table is already locked. The error message you get back is "File is in use by another". If you set reprocess to automatic, the ODBC driver seems to nicely hang your web app until the table becomes available (i.e., infinite wait).