J
john.opie
Hi everyone -
Ran into something I haven't run into before and I'm sitting here
scratching my head wondering what I can do now...
I've got a table in Excel 2000. I've got it formatted across 27 columns
and 80 rows and it is just the right size to print properly. It does so
as well: the print range is just fine. Hard copy is just fine as well.
But when I try to copy it as a picture (i.e. Shift+Edit, Copy Picture,
Picture As Printed), Excel hits me with an error message: Picture Is
Too Big and Will Be Cut.
And it does exactly that. It cuts the bottom off of the picture of the
table.
If I remove some rows (ca 6 or so), then I can copy it as a picture,
but when I resize it in the destination, it's distorted: that's why I
had those lines in there to begin with!
This is really, really weird, since we've been using this method to
transfer tables from one workbook to another (for production purposes)
for at least two years now, and have never run into this message
before.
Anyone have any idea what this might be and if there is a work-around?
Thanks in advance
John
Ran into something I haven't run into before and I'm sitting here
scratching my head wondering what I can do now...
I've got a table in Excel 2000. I've got it formatted across 27 columns
and 80 rows and it is just the right size to print properly. It does so
as well: the print range is just fine. Hard copy is just fine as well.
But when I try to copy it as a picture (i.e. Shift+Edit, Copy Picture,
Picture As Printed), Excel hits me with an error message: Picture Is
Too Big and Will Be Cut.
And it does exactly that. It cuts the bottom off of the picture of the
table.
If I remove some rows (ca 6 or so), then I can copy it as a picture,
but when I resize it in the destination, it's distorted: that's why I
had those lines in there to begin with!
This is really, really weird, since we've been using this method to
transfer tables from one workbook to another (for production purposes)
for at least two years now, and have never run into this message
before.
Anyone have any idea what this might be and if there is a work-around?
Thanks in advance
John