On Nov 8, 2007, at 10:14 PM, Heling Yao wrote:
>>> 1. when reportlib is not installed, click on the report generation
>>> menu items would cause generated app to crash.
>>
>> Does it crash, or simply exit? I know that there is code
>> in the
>> loading of the ReportLab stuff that checks if the module is
>> available, and if it isn't, print a message to the console and exit.
>
> Yeah you're right. The program just exits. I was running the app by
> clicking it and couldn't see the message. Maybe an info dialog showing
> the same message, and then let the user continue to use the generated
> app. Just a thought.
That does make a lot more sense. I've changed it so that if the
required reporting modules are not installed, the reporting button is
disabled. I will have that posted to be available for Web Update as
soon as I can test a few other things.
>>> 2. on the generated app, custom sql doesn't seem to work at all, or
>>> I'm just missing something obvious?
>
>> Also, the implementation of the custom SQL is a real hack
>> that was
>> thrown together to make it available. I mean, clicking a checkbox
>> brings up a dialog?? ;-)
>
> My bad. It does work to a certain degree. But say when I select only a
> few fields from the customer table, the edit pane becomes all messed
> up: db navigation buttons stop working and it's stuck at the first
> record; the cmd window keeps giving something like the following:
Well, that's like complaining that when you use a power drill
incorrectly, you end up with a bunch of unwanted holes. You need to
know what you're doing if you are overriding the default datanav
stuff to make sure it still works.
-- Ed Leafe
-- http://leafe.com
-- http://dabodev.com
_______________________________________________
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/dabo-users/[EMAIL PROTECTED]
