No no no no... you guys got it all wrong.
First, I don't remember the details anymore. I presume you're already doing -SOME- kind of DB access and the details should be easy to iron out with a good ADO reference handy.
Don't put the logic for incrementing the pageview counter in the ASP/VBScript. Tempting, but perhaps not appropriate. You could end up with a race condition at some point in time... yes this sounds uber-paranoid... but you should get into the habit of doing things right the first time all the time.
Cook up a stored procedure to do the incrementing. You'll have to figure out on your own how to verify that the stored proc is constructed in a manner that leaves the actual increment entirely atomic. I -believe- that a simple UPDATE statement will be atomic.
If you retreive, modify, and store without the operation (known as the critical secton) up in a semaphore of some kind then you could run into race conditions.. and that'll give bad data. Especially if you do it all the way up in the ASP/VBScript layer.
You could probably do the UPDATE statement from the VBScript layer, truth be told, but I prefer to use stored procedures rather than lop all of the schema information and SQL statements up in the uppermost levels of the app.
Although... with all THAT said I reallly hate using code to keep track of hit counts and such. A far better method, IMHO, is to parse log files to get the actual data. I've seen plenty of clients use them as the end-all-be-all of traffic counters when in reality they give you almost NOTHING of value... just a warm fuzzy feeling that may or may not mean anything.
