>Hello,
>
>I have a form which I populate using Sql Passthrough only. The top portion of the form is a grid that I use only to display the information in the main table, not updatable. I deny edition to the grid through the when event of the controls in it. The grid is used to see a lot of information at a glance or to move from one record to another or pagedowns…
>
>I have controls in the lower portion of the form that I use for updates. In my forms I let the users update more than one record at a time. I take care of sending the server the updates.
>
>Now here is my problem:
>Let’s say I update one record in the lower part of the form,
>Then I click in the grid on another record
>Then when I try and update it in the lower portion of the form I get (Record is in use by another user.)
>This may happen as I go for my second or third attemp to update information in the cursor, I still haven’t sent anything to the server I only do that when the user tells me to.
>
>The error occurs when I click in one of the combo boxes type listbox through the mousedown event or when I press a key in one of the textboxes.
>
>All the tables in the form are cursors that I get using SqlExec. They are all set to tablebuffering 5.
>
>
>More information:
>These cursors are automatically opened as exclusive.
>Nobody else has access to them since they are on my c:\temp\ directory
>I do not use the Tableupdate functions
>I do not use any views
>I use only SQL commands or calls to stored procedures
>The server is Sybase
>
>I normally run the application from the Novell server but I get the same problem if I run it on my pc.
>
>
>thanks,
>
>Rodrigo Sandoval

Without exact knowledge about the reason of this error I still would make some advices:
1. If you don't use views, then you don't need in buffering at all (I assume this is C/S application).
2. It's enough to have just one cursor which will provide recordsource for the grid.
3. Grid itself can be set as readonly, i.e. Grid.ReadOnly=.T., and you don't need in going to WHen events.
4. Textboxes showing current grid row can be unbound and populated with grid's cursor current record values from Grid.AfterRowColumnChange event.
It seems to me, that these accomodations will make your code simpler and probably eliminate the problem.