> > > >if you save the RECNO() you can just GO to it later also look at the > SEEK() > >command (as oppsed to SEEK ) in the help > > > >Arnon > > I have made it a strict programming rule for me to use primary keys to > identify records and never use recno() as primary keys can ALWAYS under any > case be assured that the record will be pointing to the same record of > interest in an event model like VFP, while recno() can not. I've gotten > burned on this a few times now and so have made the change. Is this over > reacting or do you think it makes good programming sense. > hey, hey , who ever said to use RECNO as a primary key (or any kwy for that matter)? all I said that after you change the order of a table you can return to the previous selected record by directly going to the same record number - this has nothing to do with keys I don't use recno as a key , and I don't think using it is good practice Arnon