On Mon, Oct 06, 2008 at 04:23:11PM -0500, Ed Leafe wrote: > On Oct 6, 2008, at 3:52 PM, Chris G wrote: > > > 1 - I'm getting a warning message saying:- > > > > Dabo Info Log: Mon Oct 6 21:29:40 2008: WARNING: No BasePrefKey > > has been set for this application. > > > > What's this telling me? Also, is the python traceback that follows it > > referring to the above warning or is it quite unconnected? > > Preferences are stored on a per-application basis. That's what > remembers your form positions, etc., as well as several other > settings, including any custom settings you may want to store. There's > a decent discussion of preference management at: > http://dabodev.com/wiki/PreferenceDialog > Thanks, just what I need.
> It's not critical that you do this, but it is a good practice; hence > the warning. > > > If it's relevant the traceback says:- > [snip] > > File "/usr/lib/python2.5/site-packages/Dabo-0.8.4-py2.5.egg/dabo/ui/ > > dDataControlMixinBase.py", line 112, in update self.Value = method() > > TypeError: 'str' object is not callable > > That's not related - it means that you have a bad DataSource/ > DataField combination for one of your controls. I can't tell which > from the traceback, though. > Ah, OK. It's not surprising that there are a few oddities having imported the tables from Access. > > 2 - The data from my Invoice table has some output formatting oddities > > when shown in the Dabo form:- > > > > Dab seems to think the InvoiceNumber is a 'long', i.e. it appends > > an 'L' to it. > > That's the way many values come back from MySQL. Just cast to an > int() if that's an issue. > > > Although mySql shows all the dates with a time of 00:00:00 Dabo > > shows them as 12:00:00 AM which is rather an odd time! > > One is 24hr time (00:00 to 23:59) and the other is 12hr (12:00am to > 11:59pm). This is the default format, and is stored in > dabo.settings.dateFormat and dabo.settings.dateTimeFormat. You can > override those and any other settings by creating a > 'settings_override.py' file. Look at dabo/settings.py for more > information. > OK, thanks. (I'm not at all convinced that 12:00 AM is the same as 00:00 in a 24 hour clock. To my mind both 12:00 AM and 12:00 PM are meaningless, but that's just me being pedantic) -- Chris Green _______________________________________________ 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]
