Don't. Don't even think about it.
You cannot show "the next generated primary key" because in a multi-user system (and that is the only reason to use SQL) you do not know what the "next" value will be: it depends on what everybody else is doing, and the order in which they do it. Think about it: if you have two users both entering data, then they both will see the "next" value - and it will be the same value. But when they try to submit the data, they can't both use the same primary key without SQL correctly throwing an error. You only ever show a new value after it is used, or allocated at the very least (and then you have the fun of deallocation if they don't complete the operation for whatever reason).
The "last value" is also difficult to show, unless there is some order to the keys, or some field which records the date and time at which it was allocated. Then, all you have to do is
SELECT TOP 1 customerID FROM MyTable ORDER BY ... DESC
And fill in your sort criteria. If you do not specify an ORDER clause, then SQL is at liberty to return rows in any order it sees fit - it may return the last entered, but it doesn't have to: it can happily return rows in a different order every time you run the same query, if that is more efficient for it.