Went to a SQL Server semminar by AppDev recently. The majority of the class were ACCESS programmers complaining they have run into 'brick walls' with it. Being the only VFP developer, I wondered why they didn't scale to up to VFP before taking on the added cost and complexity of SQL Server. Heard alot of groans, so I kept my mouth shut.

A lot of time was spent building a VB client server app. While I liked what they were doing with the ADO stuff, I was surprised by how much work it was. They recommended not binding any controls, hard coding INSERT and UPDATE statements and using readonly recordsets. The reason they were doing it this way was to minimize the time SQL Server maintains record locks. It was a ton of code that seemed to accomplish very little.

I'm wondering if we should follow the same logic for VFP C\S apps?

I left thinking that ADO may be a better solution for C\S because of its small footprint and MS's commitment to OLEDB and VFP cursor for file server apps.

Charlie