Frank Schönheit - Sun Microsystems Germany wrote:
Nice.
Is it just my machine that the very first form contains overlapping
controls, or is this really your intended design?
It is a problem with how the forms where constructed and setting the
zoom level it seems.
More on this as I go along on this project - but it comes down to
watching how you ANCHOR the different screen elemenets.
Also, changes made to the options/behavior form are applied, but not
shown when the form is opened the next time. Intended?
That was a hasty form / macros to demonstrate an idea...so not even
close to polished.
Furthermore, the Basic function "DeleteStr", using in onLoadForm*, does
not exist here - is this to be expected in the document, and somehow
lost? Or should it be present in every installation? Or is it something
special in one of your own Basic libs?
DeleteStr is found in the Tools library. The procedure Init.onLoad is
where I pull this library in.
Just wondering which of those artifacts are perhaps 3.1 show stoppers :)
I've been working on this file since last Wednesday and my thought was
that there might be two issues worth that status.
I believe I have a solution for one - The problem with the Open Document
event on the ODB file not firing on subsequent loads.
The cause is simple - the connection is never closed, even when the
database document is closed explicitly.
Workaround Solution - NEVER do this:
thisDatabaseDocument.DataSource.getConnection( "", "" )
instead
In the procedure Init:onLoad (in this case) that is called from Open
Document on the ODB file do:
Create a dispatch handler
Displatch the uno command to switch the database document to the tables
section.
( this gets a connection established for us)
Now only open forms using
thisDatabaeDocument.FormDocuments.getByName("formName").Open
Tonight I will make that change across the board and I believe that then
a close on the ODB file will actually dispose of the connection.
The other issue is:
Close Document event for embedded forms does not seem to fire at all.
(3.1 m7 and 3.2 m44)
My workaround is going to be to instead use the UnLoad event for the top
most dataform control instead. But that just seems wrong to me.
Drew
--
OpenOffice.org User Community Forums
Connecting users around the globe!
Community forum http://user.services.openoffice.org/en
Communauté francophone http://user.services.openoffice.org/fr
Közösségi fórum http://user.services.openoffice.org/hu
コミュニティーフォーラム http://user.services.openoffice.org/ja
United States PostgreSQL Association: http://www.postgresql.us/
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
