Hi Paul, On Mon, Jul 21, 2008 at 11:46 AM, Paul McNett <[EMAIL PROTECTED]> wrote: > > > It wouldn't hurt to try a raw dTextBox. If that still doesn't work > right, then it is likely something on your end. If it does work, then > there's something wrong with dDateTextBox. >
That was actually the workaround I had in mind since all the other Text Boxes in the app work just fine. One thing I think might be causing a problem with Dabo is that several of the DATE type fields in the db table can be NULL. My indication that this is a problem is that when the field was *not* previously NULL, I can enter data just fine, but when the field *is* NULL, it acts quirky and sometimes will let me type in the field, sometime it won't, but is always replaces what was typed with <None>, which is what was displayed initially. Also, the last time that I ran my compiled app, I got the following error: Traceback (most recent call last): File "dabo\ui\uiwx\dPemMixin.pyo", line 520, in __onWxKeyChar File "dabo\ui\uiwx\dPemMixin.pyo", line 915, in raiseEvent File "dabo\lib\eventMixin.pyo", line 93, in raiseEvent File "dabo\ui\uiwx\dDateTextBox.pyo", line 189, in __onChar File "dabo\ui\uiwx\dDateTextBox.pyo", line 217, in adjustDate AttributeError: 'unicode' object has no attribute 'toordinal' Does this shed any light on the situation? I use dTextBox for my dates and datetimes, because dTextBox works for my > needs. > When you do this, how do you check that the format of the date is SQL compatible? I guess this could be done with a regular expression, but those are more messy in Python than I wish they were. Thanks for your help, Mike M. --- 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]
