| 6:51 pm on Jul 30, 2003 (gmt 0)|
I think I would probably go with the DB route also. I guess that all depends on how much strain the db is already under from page hits and record requests.
| 6:58 pm on Jul 30, 2003 (gmt 0)|
| 8:19 pm on Jul 30, 2003 (gmt 0)|
thanks ... more unsure now!
| 8:26 pm on Jul 30, 2003 (gmt 0)|
sorry didn't mean to confuse you, just offering you my opinion ;o)
| 9:55 pm on Jul 31, 2003 (gmt 0)|
The more I think about, the more I think smokin is right. Access is so bad for Web databases, the fewer hits the better. Go with the cookie.
| 7:53 pm on Aug 1, 2003 (gmt 0)|
Are we talking about dynamic breadcrumbs?
This keeps track of the last 3 pages.
session("page1") = request.ServerVariables("URL")
| 10:44 pm on Aug 3, 2003 (gmt 0)|
I would use aspdaddy's subroutine and augment it with code to get rid of duplicates as well.
| 7:49 am on Aug 4, 2003 (gmt 0)|
Nice idea actually :) A thought I had was if the product id is stored in a querystring, you could just use a "productX" cookie and set it to the product id, rather than the URL. That way you can request the cookie and grab the product straight from the db. :)
Access is evil but I still use it :P