>Kev,
>If your PK is sequential (integer or character), you could use the TOP clause of the SQL Select command after ordering it by PK descending. If you are looking at modifications as well as insertions, then you would have to introduce some type of auditing feature to your tables. Take a look at FoxAudit at www.takenote.com.

Isn't this a rather dubious use of the PK, I thought the prevailing view was that regardless of how you implemented the PK, you should not assume any particular value. The PK is used to joins tables & nothing else.

I could be wrong here & that this is a valid use for sequential PK's, I would be interested in any views on this, being in 2 minds (or more) over use of existing unique fields as PKs or maintaining separate PKs (probably sequential).