Forum Moderators: open
1) your code is messed up and breaks during its loop.
2) Client side cookies only can store 4k (4096 bytes). If your breaking at 2 it may realize that the chain of text in the cookie can only be broken up at that part, and keeping all of it will eclipse the 4kb limit.
My suggestions.
1) make sure your source is fine.
2) Revamp the cookie to either store numerical representations of the databases, or try to reduce the overall size of data your putting in the cookie by trimming away unnecessary characters.
Remember, cookies are not the best ideas to store so much data. Perhaps you can store nothing more than a lookup value in the cookie, then have that hit a db or something that has a better formatted version of logged in databases.
hth,
mcm
The reason I'm doing it this way (believe me I'd love to do it differently) is that most of our database stuff has been built in ASPmaker. For their security settings, we have to use cookies...Unless I misunderstand. I have a post active on the ASPmaker site asking about it, but so far no response.
Thanks,
Casey
hth,
mcm
I have since also discovered that my problem is the 20 cookie per domain limit. I think as a work around, I'll be creating each cookie on a database by database basis that way each user only has one cookie at a time.
Thanks,
Casey