>For those who wonder about VFP performance on a back end database (SQL Server) Here is a recent problem I have had. When committing data to the backend, I have all of my sql passthrough statements in an array (plus the tableupdates) so that I can rollback or commit depending on whether everything is okay.
>
>I had problems because some of the sql passthrough statements that call a stored procedure to update a table were not working correctly. The problem was traced to the fact that multiple stored procedure calls, using SQL passthrough, were creating records with the SAME datetime stamp. Right down to the 1000th of a second. I had to modify the stored procedure that made the assumption that the datetimes were different.
>
>I think it would be hard to get better performance than that.

WOW! You must be running a MONSTER of a network to get that kind of performance. 64-bit maybe? Maybe not.

Although, on further consideration, I've often found that once the connection is established, ODBC performance is pretty good, even with Sybase. I just wish it didn't take as long to establish a connection, particularly with views. Why don't the views that call the same database use the same connection? I wrote an app last year where I created my own 'views' (which weren't updateable) that all used the same connection in order to improve on connection time. Anyone find a better way?