Hi Gert,

> Frank, I don’t quite understand what you mean with the above response (what
> has importing Word docs to do with column alignment? Importing Word docs has
> been working for a long time). 

You might not want to hear this :)
The very original reason for thinking about a multi-column list box is
MS interoperability: Microsoft Office documents potentially contain list
and combo boxes with multiple columns, when importing those docs, the
controls cannot properly be represented in OOo.

This does not depend at all on database access - it's purely about form
controls in Microsoft documents.

One might like or dislike the fact (I dislike it), but the need to
properly import an MS document ranks higher than the need to have some
more sophisticated controls in database forms. That is, addressing the
former is more important. (Remember that one of the great goals of OOo
2.0 was "Microsoft Interoperability"? Chances are good that this won't
change for any post-2.0 version.)

Thus, the motivation to write those spec came from "MS Interop", not
from "Database form controls". Thus, while still addressing the latter,
the main focus of the document is on the former.

> However, unless one is conversant with VB, scripting, macros and all that,
> there is no way that you can develop simple, but yet reasonably powerful
> application like you can in Access.

That is undoubted (at least by me :).

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]

Reply via email to