To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=115663
User gregmcc changed the following:
What |Old value |New value
================================================================================
Version|OOO330m14 |OOO330m15
--------------------------------------------------------------------------------
------- Additional comments from greg...@openoffice.org Thu Nov 25 23:44:32
+0000 2010 -------
Right - I have cut down the spreadsheet in which the fault is exhibiting itself
( Attached ) - As I have said in my previous messages : I can't seem to
replicate it in a clean spreadsheet. I can't believe that this is a corruption -
because surely that would move focus and come up with different errors. But I
am at a loss otherwise.
The spreadsheet YYYYmmNN_EQIC_CutDown_Rev823e50 consists of three sheets. It
is the ScheduleOfTestResults sheet that is of interest. When information is
typed into a cell the first thing it does is to call the FindRow function. This
function finds the row where a specific text exists - in this case 'Test
Instruments'. It is doing this to find the lower boundary of the table. The
table rows can be deleted or merged to suit the needs of the electrical
installation. The FindRow Function is also used to find rows in remote
spreadsheets ( when the parameters 'File' and 'Path' are set ), but this isn't
the case in this instance. If you put a hold ( a Breakpoint ) on first few
lines of the FindRow function - you be amazed to see that sSheet isn't passed
into the routine and is therefore defined as a IsMissing parameter.
If IsMissing(sSheet) Then
sSheet = Divulge("Sheet")
oSheet = ThisComponent.Sheets.getByName( sSheet )
else
If IsMissing(sFile) then
oSheet = ThisComponent.Sheets.getByName( sSheet )
else
If IsMissing(sPath) then
oSheet = oOpenRemoteSheet(sSheet,sFile)
else
oSheet = oOpenRemoteSheet(sSheet,sFile,sPath)
end if
end if
End if
And yet the 'else' aspect of the 'if' statement is the one that gets processed -
with obvious errors being generated in the 'OpenRemoteSheet' function which is
called in error ( with bad parameters ).
So this seems to be the only way that I can get the fault over to you. Please
advise ... If you don't want to swamp this 'issue' with comments and queries
you can contact me at gregmccorm...@uwclub.net - and then we can leave the core
comments on this web page.
Thanks for your help in advance - I will be really embarrassed if it is
something silly that I have overlooked - but it has been over week now since I
got stuck on this issue.
Regards
Greg McC
Liverpool, UK
---------------------------------------------------------------------
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...@api.openoffice.org
For additional commands, e-mail: issues-h...@api.openoffice.org
---------------------------------------------------------------------
To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org
For additional commands, e-mail: allbugs-h...@openoffice.org
