Milbo -
"yeh let set it to MEMORY . I like the idea to add this as optimisation tool. I think all the time that db for session is odd"
I guess you mean PHP in reference to MEMORY, which I did once and it did not seem to stop the issue, BUT I tried a SECOND TIME and it now WORKS as advertised

AH -
"Delete your session table in the dbase"
Yes I already tired that after doing some digging around the web to find out exactly what the SESSIONS package really does and HOW it does what it does, very interesting stuff BTW

Wasn't aware that one could use SESSIONS as a cracker/hi-jacker path for instance

GJC -
"In std. Joomla the session is stored in the #__sessions table.. the field has a max size and the session info can grow to quite large sizes.
If it runs out of room it is truncated and destroyed (the encrypted mangled data won't decrypt)
I remember this happening on the frontend with huge numbers of products in the cart on a site"
Thanks for the enlightening info
I did try resetting the #__sessions table and increasing DATA to LONGTEXT to no avail

It seems the real issue, for now, lies with the 'time' the application interacts with the PHP/Apache server and the Database thus causing Joomla to say "Good-Bye" and logging me out

Though it could be what you experienced also, even with the DATA set to LONGTEXT

ALL -
Changng to PHP also cleared up another issue that I was going to squawk about in that the CART was not saving the USER DATA, and would not a new user be created from the frontens or backend

VERY Annoying
Fingers crossed for now and hoping this holds together as I take the VM Cart live for the first time in years on this site
