How to change Form Properties With Code

edit

@gkick,

The arguments have nothing to do with any dialog. If recalling correctly, this argument is to set return of control after the close.

It appears you are trying to secure the application. About the best security available is to password protect the macros. Other than that it is fairly simple (need some knowledge of internals) to override things. I believe there is at least one open request to add password protection at some level(s).

@Ratslinger yes I use password protected macros, at times they execute from direct run but not when called from Cusomize, Open Doc, sometimes they do work by attaching them to the on activate event if I want to run them from the db container to do some db manipulation stuff, still learning...

@gkick,

Further testing shows no argument is needed. You can replace this part:

dim args1(0) as new com.sun.star.beans.PropertyValue
args1(0).Value = 0
dispatcher.executeDispatch(oFrame, ".uno:Save", "", 0, args1())

with just this:

dispatcher.executeDispatch(oFrame, ".uno:Save", "", 0, ARRAY())

Thanks for that, Guess one can sort of bury the actual hidden macro within other macros to make it harder to detect or remove but then ultimate security is a dream, isn it.

To further clarify, here is link to arguments for unoSave -> The UNO Dispatch Command Specifications of '.uno:Save' .

My earlier comment I confused with something else.

@gkick,

Had not tested in a while so did some basic tests with PW protected macros. Had no problem with execution from a button or direct execution from the menu. Don't know where your problems reside but may have something to do with loading libraries. This really depends on where & how you have set code & in what libraries they exist. Example:

Globalscope.BasicLibraries.LoadLibrary( "YOUR_LIBRARY" )

@Ratslinger , thanks again. Well my problem seems to be when calling the pw macro from the db containers customise open doc event. It runs from the activate and closing events where it for some reason is triggered more then once. I ll check out loading the globalscope What are the temperatures like in your neck of the woods ? Here sunny 24c.

Weather about the same as yours.

@Ratslinger Have added

If GlobalScope.BasicLibraries.hasByName("sm12") Then GlobalScope.BasicLibraries.loadLibrary("sm12") End If

to the setup macro which connects to the backend and establishes connection to the db, but does not make a difference.

Just need to run some validation prior to opening the mainform. Workaround is to pop up a splashform first, run the macro from there and close the splash, open the mainform.