>If I have table say A and another table Say B and if I want to insert records of Table B in Table A, I may do it like this,
>
>

>Insert into A.DBF (Filed1) select Field1 from Table B.
>

>
>But how to insert the Table B records if I want to insert the Table B records after the record Number 10 i.e Recno() 10 of Table A.
>
>I.e How to insert Table B records in Table A after the Table A RECNO()>10

The approach is basically flawed. You should generally consider records in a table to be an unordered set; you achieve a specific order (1) through an index, or (2) in a SELECT - SQL command, with an ORDER BY clause. In both cases, you can use different orders at different times. You might order by a field that stores a date, and you may need to add some additional fields to achieve the desired ordering.

If you physically insert records in between other records, ALL the records after that have to be moved down; for a large table, this would be very inefficient. You might do it for a very small table, but even there, I don't really see the point.

You can indeed do it - check the INSERT command (not the INSERT INTO command, which is a separate command), but it is probably much better if you don't do it. Since this INSERT command inserts only one record at a time, you would have to write a loop to insert all the records you want.