To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=97210


User npower changed the following:

                What    |Old value                 |New value
================================================================================
               Component|Spreadsheet               |vba
--------------------------------------------------------------------------------
              QA contact|iss...@sc                 |iss...@vba
--------------------------------------------------------------------------------
            Subcomponent|code                      |www
--------------------------------------------------------------------------------
        Target milestone|---                       |not determined
--------------------------------------------------------------------------------
                 Version|OOO300m9                  |current
--------------------------------------------------------------------------------




------- Additional comments from npo...@openoffice.org Mon Dec 22 11:38:49 
+0000 2008 -------
there are a couple of problems here

1. using the 'Option VBASupported 1' to trigger the vba support in an ods is
definitely unsupported. This option is really only useful when running a native
imported document. 
  a) Once a document has been saved as ods key transient information is lost
e.g. codenames and other such data. ( I am thinking about supporting this,
but... future work )
  b) in an ods document vba-mode basic could call non-vba mode code libraries
etc. mixing openoffice basic, vba-mode basic and non-mso document is NOT a good
idea :-( sorry about that

2. The problem you see is not an vba problem per. se. but to do with how and
when openoffice identifies the active document, the 'activesheet.cells' call
fails because when activesheet is called unfortunately openoffice hasn't yet
being told there is a what the active document is. 
   a) It would seem that the window of a loading document isn't 'Activated'
until after the load completes ( but I would have t investigate that further....
after Christmas that is ) 
   b) I would bet if you have a different calc document open and open the
problem document you will not get the error ( because it will thing the
previously opened document is the active one ) 
   c) Furthermore I would bet the same problem is present in general basic in
openoffice for the 'ThisComponent' variable ( in fact vba uses the
'ThisComponent' variable to determine the active docuemtn  
 

---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@sc.openoffice.org
For additional commands, e-mail: issues-h...@sc.openoffice.org


---------------------------------------------------------------------
To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org
For additional commands, e-mail: allbugs-h...@openoffice.org

Reply via email to