for the 3 weeks I m on a research nightmare. I m trying to use SQL Server 2005 and VFP and I don't know why but it is really difficult for me!!! I ve experience on VFP and SQL but very long time ago!
What I m trying to do is a multiuser application were concurrent transactions will occur in a table.
I ve read all about ISOLATION LEVELS etc. as much as my stomach can take about Microsoft SQL Server 2005. But in case of the following scenario I can't figure out what to do:
A.USER A is taking a snapshot of table Customers.
B. USER A, in Session 1 is taking a cursor of Customers tables, bringing it to the forntend (frontend will be VFP 9) and editing Customers record where Customers.id=1001.
Q1.Here I need someone please to explain me how I can place a row lock to this record (where Customers.id=1001). Is this done just by Isolationlevel and if yes, which one should I use
Q2.Does this means that noone else can touch this row (delete, update) from another session
C. USER B, in Session 2 is taking a cursor of Customers tables as well, and bringing it to the forntend (frontend will be VFP 9).
Q3. Will USER B will be able to take a cursor of customer tables (because of the lock by session 1). Should I use a specific IsolationLevel
Q4. Generally what type of isolationLevel should I use I suppose that the SERIALIZABLE is the most safe. Could I just use that as default for all statements
Any examples (including isolation etc) in VFP or SQL !! !!!! :).
Thanks for your help!
PS. I could use MySQL 5.0 if someone could so me how instead of Microsoft SQL Server 2005 Express. I ve read all the documentation but most of the VFP commands are SQL server oriented.