Hi!

Memo fields are handled different way in table than other fields. Memo field in view with buffering mode 5 will not lock the record in table. In addition, it is very-very bad practice to use BEGIN TRANSACTION at start of the form. RTFM. Transaction should last as little time as possible, when you what to have multiple users and no locking conflicts.

HTH.

>Create a simple form add a edit box make sure the control source is blank.
>
>In the INIT of the form type
> BEGIN TRANSACTION
>
>Add a table with a memofield in data environment.
>
>Set buffermodeoverride to 5 for the cursor in the data environment
>
>Place a cmd button(replace) and in click event type:-
>
> REPLACE table.memofield WITH thisform.edtreplace.value
>
>You may add an exit cmd button.
>
>Do the form within your foxpro environment(vfp 5 or 6). When the form loads click on the replace cmd button.
>
>Load another foxpro environment(2nd vfp application) do the form in this new enviroment and voila you get the message "record not available" scrolling on the status bar.
>
>
>My question is why does this happen only with memo fields and not other fields.