Re: [dba-dev] Strange behavior when loading a form using a macro.
Hi Andrew, 'oFormDoc = oFormDef.execute(sOpenMode, nCmd, eEmpty) ' Variable NOT defined 'oFormDoc = oFormDef.execute(sOpenMode, nCmd, oNull) ' Object Variable NOT set 'oFormDoc = oFormDef.execute(sOpenMode, nCmd, NULL) ' Object Variable NOT set 'oFormDef.releaseCommandIdentifier(nCmd) In all three cases, the error message was not about the last parameter, but about sOpenMode. |execute| does not take a string, but a com.sun.star.ucb.Command - sorry for the confusion, I blindly assumed it were a string. This of course (unnecessarily) complicates the macro when using |execute|. To make things worse, our implementation currently also requires a OpenCommandArgument2 to be present in the Command structure - either directly in its |Argument| member, or, if |Argument| is an array of property values, in one of the values in this array. This again is unnecessary, but sadly complicates things even more. The complete solution would look as follows: Dim identifier as Long identifier = oForm.createCommandIdentifier() Dim UcbCommand as new com.sun.star.ucb.Command UcbCommand.Name = openDesign Dim Arguments as new com.sun.star.ucb.OpenCommandArgument2 Arguments.Mode = com.sun.star.ucb.OpenMode.DOCUMENT UcbCommand.Argument = Arguments Dim environment as Object Dim component as Object component = oForm.execute( UcbCommand, identifier, environment ) This, of course, makes me to completely withdraw my statement about |execute| being easier to use than |loadComponentFromURL| :( (though I think we will do something about it, at least we should not required an OpenCommandArgument, but default it) 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]
Re: [dba-dev] Strange behavior when loading a form using a macro.
Thanks! Frank Schönheit - Sun Microsystems Germany wrote: Hi Andrew, 'oFormDoc = oFormDef.execute(sOpenMode, nCmd, eEmpty) ' Variable NOT defined 'oFormDoc = oFormDef.execute(sOpenMode, nCmd, oNull) ' Object Variable NOT set 'oFormDoc = oFormDef.execute(sOpenMode, nCmd, NULL) ' Object Variable NOT set 'oFormDef.releaseCommandIdentifier(nCmd) In all three cases, the error message was not about the last parameter, but about sOpenMode. |execute| does not take a string, but a com.sun.star.ucb.Command - sorry for the confusion, I blindly assumed it were a string. This of course (unnecessarily) complicates the macro when using |execute|. To make things worse, our implementation currently also requires a OpenCommandArgument2 to be present in the Command structure - either directly in its |Argument| member, or, if |Argument| is an array of property values, in one of the values in this array. This again is unnecessary, but sadly complicates things even more. The complete solution would look as follows: Dim identifier as Long identifier = oForm.createCommandIdentifier() Dim UcbCommand as new com.sun.star.ucb.Command UcbCommand.Name = openDesign Dim Arguments as new com.sun.star.ucb.OpenCommandArgument2 Arguments.Mode = com.sun.star.ucb.OpenMode.DOCUMENT UcbCommand.Argument = Arguments Dim environment as Object Dim component as Object component = oForm.execute( UcbCommand, identifier, environment ) This, of course, makes me to completely withdraw my statement about |execute| being easier to use than |loadComponentFromURL| :( (though I think we will do something about it, at least we should not required an OpenCommandArgument, but default it) Ciao Frank -- Andrew Pitonyak My Macro Document: http://www.pitonyak.org/AndrewMacro.sxw My Macro Book: http://www.hentzenwerke.com/catalog/oome.htm Free Info: http://www.pitonyak.org/oo.php - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[dba-dev] Embedded Database and User accounts and Schema's
A few questions regarding User accounts and the embedded HSQL database engine? I suppose I can boil it all down to - Will they be supported or not? Here I am NOT talking about supporting concurrency or record locking - gotta let the folks at HSQL have at that first I suppose. I am just talking about OOoBase recognizing and utilizing the support for USERS, ROLES and PRIVLIDGES that already exist in the engine. Currently I am running OOo 1.9.118 and finding that their is partial support for this functionality but not to the point that I would need for my purposes. (with the biggest problem being that both the GUI and API access to the embedded database engine ignore USERNAME and PASSWORD settings...big problem there) There are many times when building an application one would want to have a user account that has use of certain objects, but not the ability to edit those objects. The same question goes for the use of SCHEMAs. Here it is a bit less bothersome, as I am already using the funtionality in the engine and it is working as expected. However at the GUI level there is no recognition of the schemas..i.e. all tables and views are listed from all schemas...if you try to open a table that is in a schema that you are not currently in you will be blocked from doing so...but other then this USING schemas works fine. Thanks for your time in advance Andrew Jensen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[dba-dev] OOo driver for Embedded Data
This is a similar question to one posed earlier regarding Crystal Reports but in broader terms. Are there currently any plans to implement either a JDBC or ODBC driver for access to the data in an Embedded database file? Thanks Andrew Jensen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
