Hi Andrew, >>Ah, that sounds interesting. Having a button in a form saying "How do I >>do this" which, when clicked, opens the help page ... would be quite cool :) >> > If I am not mistaken ( and I often am ) use of the XHP format files will > allow us to call up these help files in the standard way F1, no need for > special buttons.
Yes, we probably can. I just imagined some more ... obtrusive :9 way of saying the user "You wonder how this cool thing works? Click here!". It doesn't have to be some animated character ;), but F1 might be to hidden. But well, that's not really the most important design decision to make ... > I have not heard much about a scenario for the database, does anyone > have any ideas on this or comments on what I have proposed so far. I'm not sure I'd call "Plato Total Health Systems" a small company, given the complexity of their business processes, as I understand them. (But hey, what do I know how businesses really look like from the inner? :) What I, ehm, wanted to say with this: I'm not sure this scenario isn't too complex already. While it might be realistic, I'm not sure that all bells and whistles of the current scenario are useful for explaining something to the user. That is, if we can't use a certain piece of the business process particle of this company to answer at least one common "How can I do ..."-question in Base, then should we really introduce this particle to the scenario? Not sure. For instance, I'm not sure about the actual benefit of the external web hosting company. Also, I think I already touched this somewhere: Do we want to have a single database file, or a bunch of files which comprise the whole "business intelligence application"? I tend to the former, but again might not have enough insights into real-world usage scenarios to know whether this is sufficient. Do others here have opinions? Ciao Frank -- - Frank Schönheit, Software Engineer [EMAIL PROTECTED] - - Sun Microsystems http://www.sun.com/staroffice - - OpenOffice.org Database http://dba.openoffice.org - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
