B
Bill Ridgeway
I recently posted a query regarding a spreadsheet which displayed "#N/A" in
error from a reference to a worksheet in another spreadsheet - but only when
the source spreadsheet wasn't open. Suffice to say the formula is a
straight =(a cell in another worksheet in another spreadsheet) which works
OK in other cells.
The formats in the source worksheet were copied down but the error persisted
in only the one cell. Formats in both the source and target cells were
copied down again resulting in the error persisting in only the one cell. I
found that the problem resolved by deleting just one character in the source
cell.
Several people responded to that thread which, as it unfortunately didn't
lead anywhere, I compromised by just omitting the 'rogue' character.
Unfortunately the problem has re-emerged. Now, not only does the original
cell return "#N/A" but also, intermittently do two others and a further cell
returns part information and a string of "squares....squares".
There seems no rhyme or reason for this error and I would appreciate any
insight as to a possible cause.
Regards.
Bill Ridgeway
error from a reference to a worksheet in another spreadsheet - but only when
the source spreadsheet wasn't open. Suffice to say the formula is a
straight =(a cell in another worksheet in another spreadsheet) which works
OK in other cells.
The formats in the source worksheet were copied down but the error persisted
in only the one cell. Formats in both the source and target cells were
copied down again resulting in the error persisting in only the one cell. I
found that the problem resolved by deleting just one character in the source
cell.
Several people responded to that thread which, as it unfortunately didn't
lead anywhere, I compromised by just omitting the 'rogue' character.
Unfortunately the problem has re-emerged. Now, not only does the original
cell return "#N/A" but also, intermittently do two others and a further cell
returns part information and a string of "squares....squares".
There seems no rhyme or reason for this error and I would appreciate any
insight as to a possible cause.
Regards.
Bill Ridgeway