We have a rather old application that uses an early version of Reactor (vintage 2006-ish). It works fine with SQL 2000 in the development environment. We don't get many change requests for this app so while it gets a lot of use in the production environment, things on dev and staging are pretty quiet. Recently I had to make an extremely minor content update and it turned out that the staging box version had an issue inserting a new user, a problem we could not duplicate in development or production.
When I compared the the Reactor code it turned out that it was different for this part of the application. The user table is using some defaults and they were not picked up in the Reactor code. The client, who has control over the staging environment, updated the database to SQL 2005 some time ago and my suspicion is that our version of Reactor can't cope. I'm wondering if anyone out there is using a newer version of Reactor and can confirm that it works fine with SQL 2005. Also of course I'm trying to gauge the risk and effort involved with updating Reactor to that newer version. Would I have to replace the whole thing or are we talking about something akin to a plugin for 2005? Thanks in advance for your insights, Caroline Wise ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Want to reach the ColdFusion community with something they want? Let them know on the House of Fusion mailing lists Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:325017 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
