Are bookmarks commonly used to uniquely identify records? They seem to be objects, and not
exactly unique numbers. So, if I wanted to send some data using POST, such as a record ID,
I couldn't exactly send a bookmark. And it seems some recordset objects don't support them.

Do most people, in general, use a special column, to store unique IDs for records? Such
as an auto-increment column?

No, bookmarks are not used to uniquely identify records, that is the job of the primary key field(s). If you need to pass info around to identify a particular record then you need to pass around the primary key value(s).

Your question "Do most people, in general, use a special column, to store unique IDs for records? Such as an auto-increment column?" can be the subject of religious wars. Some people believe in this method, others (myself included) believe in using a natural key wherever possible.

Whichever way you choose to go, the important thing is that you uniquely identify each row by some form of primary key (whether that be a natural key or a generated key), not by a record's position.

hth
Phil

Thanks for the info. I wasn't aware of it. :)

I was kind of forced to use the auto-increment key design because it was one of the first examples of a simple database editor I found on the web. But, natural keys seem like a better choice. Found some articles comparing the two.

That is to say, they seem to be a better choice (for my purposes). :)