On Friday, September 09, 2011 11:52:48 am Ed Leafe wrote: > On Sep 9, 2011, at 1:44 PM, Paul McNett wrote: > > Had this feature been in Dabo, the control would have found the default > > value from the bizobj (bizCustomers.DefaultValues["waiver_mode"]) and > > went ahead and changed the value in the bizobj. > > > > Now, the real problem was my neglect, so I'm on the fence as to whether > > my idea is good or not. > > It seems to me like the correct solution would be a one-time database > update script, unless I'm not seeing the whole picture. Also, if the > problem wasn't bad data in the database, but a poorly-defined dropdown, > wouldn't there be a potential for changing valid values to the default > value? > > > -- Ed Leafe
Yes what you say is correct. However, Dabo has in the past has eased the developers plight by making it easier to recover from the error when the developer shoots himself in the foot. All of us have run into this problem. If there is a solution or way to recover from the error I'm in favor. Johnf _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-dev Searchable Archives: http://leafe.com/archives/search/dabo-dev This message: http://leafe.com/archives/byMID/[email protected]
