>The reason that 'go top' seems to fix things for you is that by moving the record pointer with record-buffering that commits the data when the record pointer changes is that your 'go top' commits the data - if you were using table buffering or allowed multiple uncommitted record changes to accumulate, 'go top' would not fix things. This ties in with the logic of needing to change buffer modes when generating or rebuilding indexes on views.



If i Have a Table Buffering .... the table will receive the changes only if i issue a table update .... a siple GO TOP or SKIP commits changes only if i have some changed in current record with record buffering .....

Is Something wrong on my thouguth ??