Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
A Strategy
Message
From
16/03/2001 21:59:39
 
 
To
All
General information
Forum:
Visual FoxPro
Category:
Databases,Tables, Views, Indexing and SQL syntax
Title:
A Strategy
Miscellaneous
Thread ID:
00486199
Message ID:
00486199
Views:
48
Need some help from you guys or gals out there. Here is my situation with the application I have been building. The application contains multiple dataentry form as well as form which are primarily for query and then updating the tables - no data entry required updating is done in the code. In the initial part of the data entry form one record in enter in a cursor and then when user goes to save I query a view for the id the user enters for the subscriber table and then I append a record to two other tables. All the tables are optimistic row buffering. After that I have all the table wrap in a transaction with rollback. In the second part of the form I have a view with is table buffered the user is allowed to edit and save. The data comes from all the information they have entered in the first part of the form. The user isn't allowed to move to next record in the grid without saving. It also has a transaction which sends back to the table. Now as I understand it during a transaction if a user tries to save while another user is perform the same save on the same table they will get a message from foxpro "table in use..please wait". As soon as the first user has save then the second user will be able to save. This seems to be ok since they are only saving one record. However, if user one has change the same field as user two then we get a multiuser conflict situation which I must deal with. I believe that right but am not exactly sure about foxpro message. This all seems to be working ok since I had several users on the application today and didn't see any problems. Now on the grid which is table buffered when FoxPro goes to update will it be only checking for the one record that is changed and sending the change back. Do you see any problems there - the recordset is probably about two hundred records. Now other non data entry form I can have a recordset with 20,000 records. I have a non updateable view which queries for the criteria and then I scan thru the view seeking the record in the original table (update it) and then append records to several other tables and then perform a transaction for each record. Originally I had a view which was table buffered but found that when I went to update it was to slow. Sorry this is so long but what do you think? Thanks Hope I have explained it.
Next
Reply
Map
View

Click here to load this message in the networking platform