Peter Seckler wrote: > Ed Leafe wrote: > >>> On Jan 13, 2009, at 10:32 AM, Peter Seckler wrote: >>> >>> >>>> yes, I thought about something like that and it should do the trick >>>> (instead of 'null' I'd take an empty string). The Problem is with >>>> date or integer fields where there is no value that could represent >>>> NULL. I'm going to have to think about a way around it... >>>> >>> In other contexts, I've seen a checkbox by the field that someone >>> would check to indicate "no answer" (i.e., null) instead of a blank/ >>> zero value. You could also add a context menu to the controls with an >>> option to set the Value to None. >>> >> Or a keypress, or... >> >> We could also consider adding a context menu item in the dabo framework to >> set the >> value to None, along with a corresponding property "ShowSetToNone". >> >> Paul >> >> > > Ok, thanks for the ideas! I am going to try them out. > > Peter > Hhhmmm! I would hesitate about the context menu. Explicit is better than implicit. If I had an application relying on a Null option in a context menu then it would have to be made very clear in the manual and in training. And still I wouldn't be surprised at the user not using it. I'd rather go with the checkbox option. Though I'd prefer the traditional VFP approach. Controls default to None value unless explicitly set, and None values show as empty, so a date with a None value would show as " / / ", and a number as " . ". Then if the user deletes everything in the edit box and <enter>s it would be assumed he means a Null value (I'm not sure if this part is in accordance to VFP but I like it).
--- StripMime Report -- processed MIME parts --- multipart/alternative text/plain (text body -- kept) text/html --- _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users Searchable Archives: http://leafe.com/archives/search/dabo-users This message: http://leafe.com/archives/byMID/[email protected]
