After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 552750 - cannot reference cell in another workbook: "Unknown workbook" error
cannot reference cell in another workbook: "Unknown workbook" error
Status: RESOLVED FIXED
Product: Gnumeric
Classification: Applications
Component: Main System
1.9.x
Other Windows
: Normal normal
: ---
Assigned To: Jody Goldberg
Jody Goldberg
Depends on:
Blocks:
 
 
Reported: 2008-09-18 09:10 UTC by John Comeau
Modified: 2009-03-28 15:40 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description John Comeau 2008-09-18 09:10:23 UTC
Please describe the problem:
When entering into a cell in Book3.gnumeric: "=[Book2.gnumeric]Sheet1!A1", you get the error "Unknown workbook 'Book2.gnumeric'". If you use the documentation example, only Book2 without the .gnumeric extension, same thing: "Uknown workbook 'Book2'".
This appears to be the same bug as closed bug 361516, supposedly fixed in 1.7.

Steps to reproduce:
1. Create and save two workbooks, Book2.gnumeric and Book3.gnumeric. Leave them both open during this test.
2. In Book3, Sheet1, Cell A1, enter: =[Book2.gnumeric]Sheet1!A1
3. Error dialog pops up


Actual results:
Error message forces "Re-edit" or "Accept". Selecting the latter inserts a single quote before the "=", rendering it as text rather than a cell reference.

Expected results:
It should fetch the cell contents from the other workbook as the documentation indicates.

Does this happen every time?
Yes.

Other information:
I had one instance where it almost worked. I was using: =B4-['Water Meter Readings 2007']September!B4. A number (0) appeared in the cell. No error message. I clicked back on the cell and the workbook name had been normalized to Water%20Meter%20Readings%202007.gnumeric. I corrected the worksheet to December, and got the error message. I retyped the workbook name as before, still the same error, and haven't gotten it to work again since that one fluke. This is the Win32 build of 1.9.1.
Comment 1 John Comeau 2008-09-18 09:31:07 UTC
Same using 1.9.3-20080908 from Jody's binaries page.
Comment 2 Morten Welinder 2008-09-18 22:41:27 UTC
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


*** This bug has been marked as a duplicate of 550898 ***
Comment 3 John Comeau 2008-09-19 13:20:26 UTC
Bug 550898 supposedly was fixed 20080904. I installed Jody's 20080908 build and my bug is present. Also, bug 550898's poster said his problem didn't exist in 1.9.1, and my problem does.
Comment 4 John Comeau 2008-09-20 03:07:46 UTC
Reopening bug due to the previously mentioned observations. It doesn't seem to be resolved by the 20080908 build.
Comment 5 Morten Welinder 2008-09-22 14:58:21 UTC
Jody: was your Sep 8 build up to date with goffice?
Comment 6 Jody Goldberg 2008-09-23 20:55:49 UTC
It included
2008-09-04  Morten Welinder  <terra@gnome.org>

        * goffice/utils/go-file.c (go_url_resolve_relative): Fix
        references to wrong URI.  Fixes #550898.
Comment 7 Morten Welinder 2008-09-23 21:02:58 UTC
Ok, in that case something else is wrong.  Is your build debugable?
Comment 8 Jean Bréfort 2008-10-17 15:29:57 UTC
I can't reproduce the bug as describe, but if a space is added to the sheet name, gnumeric.exe crashes (something as '=[book2.gnumeric]Sheet 1!A1').
Comment 9 Morten Welinder 2008-10-17 15:49:16 UTC
Crash from comment 8 fixed.  (s/book2/Book2/, btw.)  The crash was unrelated.
Comment 10 Jody Goldberg 2009-02-06 03:17:46 UTC
Can't replicate crash with 20090205 build, but the waters are muddy here.

Is the original bug fixed ?
Comment 11 Andreas J. Guelzow 2009-03-28 05:48:45 UTC
John??
Comment 12 John Comeau 2009-03-28 14:59:12 UTC
Sorry, no longer using Windows, and the bug didn't exist in Linux last I tried.
Comment 13 Andreas J. Guelzow 2009-03-28 15:40:55 UTC
Congratulations on no longer using Windows. We'll assume the bug is indeed fixed now.