>Currently writing a routine that batch inserts records from VFP to SQL using a stored procedure and the INSERT INTO command. I was shocked to see that the SELECT statement (after running the inserts) returned a cursor with the records in no particular order.. if the SQL table is cleared and then the inserts are run again.. the records are again in a different order.. none of which match the original VFP physical order. Any suggestions? Is the idea of 'physical order' dead once you move to SQL and you have to rely on identifiers, orders, and/or indices? Thanks in advance -- Len

You are correct there is no 'physical order' in SQL Server in general. If table has a clustered index than records will be physicaly ordered because data is stored with clustered index.