Hi Bernard.

Thanks for sharing your experience. Some additional questions below.


>--The only "problems" I had which I worked around is that since we use a single connection, sometimes VFP moves too fast when there are a number of CA's so the connection shows up as busy. You have to have a wait loop.

Have you set the fetchsize to -1 and maxrecords to -1 ? If so, then it sound strange to find the connection busy (Bug?). What exactly is your workarround?

>--You have to cater for SQLServer's page locking which sometimes causes blocking if a number of users update at the same time.

I guess that is not really a problem of the cursor adapter, but rather of SQL server. So you have a way of detecting and resolving a deadlock? How is this specifically implemented?

>--Also SQLServer will give an error if a field name is used that is a reserved word e.g.a field called PLAN
>I solved this and catered to all such future additions of reserved words by enclosing ALL field names with square brackets [PLAN] works. Since I built this into the builder (Mark's) it was a case of change once and reap the rewards.

I'm aware of that problem. We have unique fieldnames that have a three character prefix, so each field in the database has a unique name and does not clash with reserved words.

>I still use the CA builder Mark did for VFP8 although we use VFP9
>You can download the VFP8 one (the one I modified) from
>http://www.foxite.com/downloads/default.aspx?id=161


>and the VFP9 one is here:http://www.foxite.com/downloads/default.aspx?id=162

Thanks

>A Tip:
>I have adapted the VFP8 one to use SQL Views as well as I hate having to construct SQL statements for different cases. I just create Views rather that complicated SQL statements. So while the database is normalised, I have views for the hard lifting so that I don't need complicated joins for them.

Not sure whether I understand what you mean here.

Walter,