Hi!

Ok, what about non-structural and non-compound indexes in IDX files? Before editing close index, save data, than open index again. Because index file was closed for duration of editing, old index order is used. This could not work, however, in certain cases - VFP have a lot of conflicts in transaction commands and with 5-th buffering when working with such indexes. Just an idea.

Another idea is to sort that table on the required order if it is not too large. Index it, copy to another table with that index set so the copy will be phisically sorted properly, delete old file then rename new file to the old name, than use. Now records are in required order without any index. For quick search, set the order in the another alias for the same table and search there, than use recno() to go to the record in the main alias displayed in the grid. Above way search will work with the latest information, and the data will not be re-ordered.


>>Hi!
>>
>>If this is a table - well better of you use a query...
>>
>>The idea is simple - query the Street field twice. First field is editable and you display it in the grid. Second field is read-only and used by index only for search. This way when you change the street the field order will not change until you requery the data.
>
>Hi Vlad,
>
>I thought about this idea, but dismissed it for several reasons... One of them is, that we have predefined table structure, which I can not change. Another is: I allow to change ccode, town, stNum, Unit, StNumExt as well. All of these fields are part of the index.
>
>I was thinking in the direction of saving nPrevRec and nNextRec in form properties and change next/prev methods. But it's also not absolutely clear for me, though I tried to think it through this weekend (no coding, just thinking :))
>
>In our framework and for the particular application, I was having in mind, we use tables directly and apply filter on it, if needed. The table structure is predefined. The table is aliased as BldMstr.
>>
>>
>>>Hi Vlad,
>>>
>>>Seems like I didn't explain the problem well. Ok, I'll try again:
>>>I have a table with index set. I change one of the fields, which index is based on. Now I'm not at the place, I was before, but in the different place in the file. E.g. I was on streets starting by "A", I changed one street to start from "T" and when I press Next\Prev button, I'm now on "T" letter in the file. I want to still be on "A" to continue my work...
>>>
>>>Thanks in advance.
>>>
>>>>Hi, Nadya!
>>>>
>>>>It is not clear for me what is the problem. What means 'I want to remain on A'?
>>>>
>>>>>Hi everybody,
>>>>>
>>>>>I have the following situation: I have a grid with ability to edit couple of fields. The table has an order set to Situs (upper(ccode+town+Street+str(Snum,4)+StNumExt+Unit). Suppose, user changes street from Aitlor (typo) to Tailor. Now when he/she presses the next/prev button on the navigation bar, he/she moves to another position in a table. I want to remain on A. It doesn't matter, if I have editable grid or editable textboxes, the problem exists for both cases, though grid case seems to be more complicated.
>>>>>
>>>>>Do you have ideas, how to save the current context?
>>>>>
>>>>>Thanks a lot in advance.