Hi Tore.
Generally I would agree with you, but I think there will ALWAYS be an exception . Indeeed, is'nt it the Exception always proves the rule !!
In this partcular case, its an existing app with 1000's of lines of code, the Table thats being inserted against will never be more than 20/30 records and the customer requires an Insert option.
The options are:
1. Redesign completetrly the exisitng APP , intoduce indexes where thre were none , with a big chance of breaking it, and also investing perhaps 3 or 4 days in redeveloping and testing

2. Introsuce about 5 lines of Code (INSERT BLANK BEFORE) being one of them, and as far as I can see this will do the job.

I am inclined to go for Option 2.

Regards,
Gerard






>Rule # 1: Never make an application where the record number is important, use index tags instead.
>Rule # 2: If the record number is important, rethink your design and see rule # 1.
>Rule # 3: There are NO exceptions to these rules.
>
>>ok Sorted this.
>>It appears that if the table has any index file associated (even though you have not Set Order to) , it always appends the row
>>If all Indexes are removed from the table, it works fine
>>
>>
>>>Hi.
>>>I have a small basic DBF with a few fields and I want to insert a row
>>>I position myself on the 3rd row OF 10
>>>No indexes are on
>>>
>>>INSERT BLANK BEFORE
>>>
>>>but it appends a row at the end (i.e. 11th record instead of being the 2nd record)
>>>I know I have done this in the past , but cant get it to work today.
>>>What am I missing ?
>>>
>>>Tia
>>>Gerard