Hi!

Well, why you need that index? When you just need sort order, put 'ORDER BY seq' clause in the SELECT statement of view. If you need it for quick search, again, it is not needed, unless your view contains >10,000 records. Just index each time berfore search when index vanished.
When view contains large number of records... well, I cannot help you here, if you really need 5 buffering mode. You may try to build view over view, 1-st level view will have 5 buffering mode and will be used only to send updates in a batch, 2-nd level - will have 3-d buffering mode, just for indexing. (I never tried it so cannot say if it is possible to organize without problems.) In addition, I cannot imagine situation when such view with large number of records is needed in new application, specially with table buffering mode. You moved from local database to SQL Server?


>Thanks Vlad
>
>Your suggestions have pointed me in the right direction.
>
>However I do need table buffering because this app my be upsized.
>
>I followed your suggestions below here is my code
>
> CURSORSETPROP("BUFFERING", "v_tickitm", 3) && row buffering
> SELE v_tickitm
> INDEX on seq tag seq OF (c:\temp\test) ADDITIVE
> CURSORSETPROP("BUFFERING", "v_tickitm", 5) && table buffering
> =requery('v_tickitm')
> set order to tag seq in v_tickitm
> if order('v_tickitm')<>'SEQ'
> error 'Order is not set to SEQ'
> endif
>
>
>This works fine but later on I find my index has vanished again and I am having trouble finding out at what point this is happening.
>