I missed the beginning of this thread, but for what it's worth, I found the client variable removal tool of dubious value. I did a bunch of experimentation a while back and developed a bunch of tricky code to migrate client variables from a registry to a database on an application I inherited.
The tool for client variable removal mentioned below left a lot of client variables behind. It's also my understanding that they will expire eventually anyway and be cleaned out in the 'normal' fashion. I suppose you would set up a new data store for your new client variable storage, enable it for client variables and leave the old store defined - adjust the old store's expiration period to one day, wait and then they'll disappear? Haven't tried this - just a suggestion. Chuck McElwee etech solutions inc www.etechsolutions.com -----Original Message----- From: Christine Davis [mailto:[EMAIL PROTECTED]] Sent: Wednesday, March 20, 2002 2:39 PM To: CF-Talk Subject: RE: Removing client variables from registry I'm currently working on this issue and found the following articles helpful: Info on Error 1450 http://www.macromedia.com/v1/handlers/index.cfm?ID=22078&Method=Full Tools for removing client registry variables http://www.macromedia.com/v1/handlers/index.cfm?ID=20340&Method=Full Recommended client variable setup http://www.macromedia.com/v1/handlers/index.cfm?ID=21170&Method=Full Thanks, Christine Davis [EMAIL PROTECTED] http://dbdesigns.dragonbait.com 978-374-5438 ______________________________________________________________________ Structure your ColdFusion code with Fusebox. Get the official book at http://www.fusionauthority.com/bkinfo.cfm FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
