Created attachment 169444 [details] Win10 Split db LO6.4.7 HSQL2.51 auto setup macro hiding db conainer Hi, Basic procedure finds and connects the backend, logs in the user and calls a procedure to hide the database container, the procedure then opening a form. The form contains command buttons to open another form, a report and an option to display the database container. Closing the secondary form or the report will also close the calling form taking the user back to the desktop while the process is still running in the background. As such it is not possible to build a functional menu system. Please refer to the attachment for reproduction This applies to Lo 6.4.7 and earlier, have not tested on 7+
The split db contains an auto setup macro calling a routine to hide the db container which in turn opens a form. Closing a called form or a report will also close the calling form returning control back to the desktop yet leaving the process behind. As such it is not viable to build a functional menu system.
*** This bug has been marked as a duplicate of bug 140151 ***
Sorry my bad, I incorrectly closed this as a DUP, reset as unconfirmed.
Attachment isn't a Split DB and has nothing special to do with Windows. You haven't set a macro to switch form "blah" back to "Instruments". You only close this form with .uno:CloseDoc. But the form "instruments" you closed when opening the form "blah". So no form is available afterwards and also the main window is unvisible as you have set it after starting the Base document. I don't see a buggy behavior here.
(In reply to Robert Großkopf from comment #5) > Attachment isn't a Split DB and has nothing special to do with Windows. > > You haven't set a macro to switch form "blah" back to "Instruments". You > only close this form with .uno:CloseDoc. But the form "instruments" you > closed when opening the form "blah". So no form is available afterwards and > also the main window is unvisible as you have set it after starting the Base > document. > > I don't see a buggy behavior here. No response, so let's assume no bugginess and close.