Word Cannot obtain the data from the excel.sheet.8 link.
kt32707
paste special, then clicking the paste link option and then selecting
unformatted text. When I do this, it get Word Cannot obtain the data from the
excel.sheet.8 link.
This happens with any option when paste link is selected. When paste is
selected it inserts the data.
This normally works. We move the files around, and use a macro to change the
path when the file is opened: SetLinkedImagesLocalPath(). The existing links
work fine. Just can not insert new ones. If I do it the old fashioned way in
type out the {LINK } field, it works fine also. My users will not go for
having to type the link field out.
Anybody know why this is not working?
--
KT
kt32707
having the problem, the ones that do not have named fields do not. I have to
use named fields as we often insert and delete rows and columns. Without the
named fields, we would always be updating the link in word which would not be
acceptable.
--
KT
kt32707
same document using word 2003 with service pack 2, it worked correctly.
Is this a service pack 3 issue?
--
KT
cuthbe...@bigfoot.com
I'm having the same problem (as are others).
I've also noticed that Excel sheets in Word 2003 SP3 linked to a named
range print out poorly with unevenly spaced characters. As soon as the
link is removed the printing is fine. In fact, if the link to a named
range is replaced by a link to cell range, the problem of uneven
spacing disappears.
Ian
Bob Buckland ?:-) At Beautiful Downtown
The error message in the subject does appear that this is an issue that is related to Office 2003 Service Pack 3 when pasting named
ranges from Excel.
At present the workarounds that have bee reported include -
1. Use the cell range rather than a named range to pick and paste.
2. Similarly, once you have a working link in word if you press Alt+F9 to view field codes and edit the field code to use (add in)
the named range then it also works.
The additional item below, regarding character spacing isn't a variant I'd seen mentioned before. Are you saying the whole document
prints out poorly with the linked item? What font and what printer are you using?
===========
>><cuthbe...@bigfoot.com> wrote in message news:3331ed71-a7fb-4441...@w34g2000hsg.googlegroups.com...
Ian>>
--
Bob Buckland ?:-)
MS Office System Products MVP
*Courtesy is not expensive and can pay big dividends*
kt32707
Does your first comment mean that it is not an office SP3 issue or is it
just that the subject does not indicate it is a Sp3 issue? The reason I ask,
is that on SP 2, you can paste an excel named range with no errors, but with
SP3 you get the error that is in the subject line.
Using the cell range to do the paste is not acceptable. If a cell is moved,
the link breaks.
Your second option is to un-name the cell, paste, name the cell and change
the link. I have close to 100 links in my document and I create one of these
documents a week. That would add a lot of time to my process and I get paid
by the job, not the hour.
Is this being reconginzed as a bug and going to be corrected? I was just
about to port my company over to using the functionality instead of SET/REF
statements because it reduces writing time by about 10%, again this is per
week...
for now, I would like to roll back to office SP2...
--
KT
kt32707
one of the other users had found, but never had been able to complete it. It
was not clear to me what to do as the registry keys and hives referenced did
not exist and it did not say anything about having to add them.
http://support.microsoft.com/default.aspx/kb/938815
If this corrects the problem please respond with what was done.
--
KT
cuthbe...@bigfoot.com
driver and a Microsoft driver for the Kyocera printer, and an HP
printer driver and Adobe Acrobat 7.0 pdf driver. I have tried
different fonts - Arial, Trebuchet, Times New Roman - to remedy the
problem without success.
Like other posters, I feel the workarounds suggested are
unsatisfactory. Ironically my specific reason for upgrading to Office
2003 was to improve linking performance, which was successful until
the SP3 update.
Sorry about the delay in replying.
Ian
On Nov 21, 8:15 pm, "Bob Buckland ?:-\)" <75214.226(At Beautiful
Downtown)compuserve.com> wrote:
> Hi Ian,
>
> The error message in the subject does appear that this is an issue that is related to Office 2003 Service Pack 3 when pasting named
> ranges from Excel.
>
> At present the workarounds that have bee reported include -
>
> 1. Use the cell range rather than a named range to pick and paste.
>
> 2. Similarly, once you have a working link in word if you press Alt+F9 to view field codes and edit the field code to use (add in)
> the named range then it also works.
>
> The additional item below, regarding character spacing isn't a variant I'd seen mentioned before. Are you saying the whole document
> prints out poorly with the linked item? What font and what printer are you using?
>
> =========== >><cuthberts...@bigfoot.com> wrote in messagenews:3331ed71-a7fb-4441...@w34g2000hsg.googlegroups.com...
Sean
will not let you ember a named range - its just embeds the RC reference but
not the name. I am desperate to find a solution to this (desperate to have
wasted $400 on an upgrade!). Does anyone have a solution?
Sean
cuthbe...@bigfoot.com
> Well; here's some great news - upgrading to Office 2007 won't help. It too
> will not let you ember a named range - its just embeds the RC reference but
> not the name. I am desperate to find a solution to this (desperate to have
> wasted $400 on an upgrade!). Does anyone have a solution?
>
> Sean
>
It is very interesting that OLE was a big flagship technology a few
years ago, this thread is about it not working properly following an
application upgrade (to SP3 and to Office2007), and there appears to
be no-one who cares? Does nobody use links to named ranges?
Ian
scottherold
EggHeadCafe - .NET Developer Portal of Choice
http://www.eggheadcafe.com/default.aspx?ref=ng
macropod
Perhaps it's a user error - this NG is for application errors.
--
Cheers
macropod
[MVP - Microsoft Word]
"Scott Herold" wrote in message news:200911319...@comcast.net...
Pancho Pancho
First I want to tell you there is a much easier way to have data from excel feed into a word document e.g. you may have a word document that contains figures from an assessment you do on a regular basis - the only thing that changes is the figures, not the text. You can put all your figures in an excel spreadsheet and then update the document with the figures.
All you do is copy a value from excel (in one cell) or a whole table.
And in word you click paste special (under the home tab). Here choose paste link: they give you some options but I just say paste unformated text. )
So this can work for data in cells.
Unfortunately it does not work for Figures : Word throws out the error you refer to.
Instead, you should copy the figure from Excel and do a regular Ctrl + V paste into word. Then, you will notice click on the little clipchart next to the figure and select the linkage of data:
For more details check out the link below:
http://office.microsoft.com/en-us/word-help/copy-excel-data-or-charts-to-word-HP010198874.aspx
Thanks!
>> Additionally, it appears that the fields that are named fields in excel are
>> having the problem, the ones that do not have named fields do not. I have to
>> use named fields as we often insert and delete rows and columns. Without the
>> named fields, we would always be updating the link in word which would not be
>> acceptable.
>> --
>> KT
>>
>>
>> "kt32707" wrote:
>>> I am using Word 2003 with Service pack 3. When I tried this at home with the
>>> same document using word 2003 with service pack 2, it worked correctly.
>>>
>>> Is this a service pack 3 issue?
>>> --
>>> KT
>>>
>>>
>>> "kt32707" wrote:
>>>> On Oct 31, 3:10 pm, kt32707 <kt32...@discussions.microsoft.com> wrote:
>>>>
>>>> I'm having the same problem (as are others).
>>>>
>>>> I've also noticed that Excel sheets in Word 2003 SP3 linked to a named
>>>> range print out poorly with unevenly spaced characters. As soon as the
>>>> link is removed the printing is fine. In fact, if the link to a named
>>>> range is replaced by a link to cell range, the problem of uneven
>>>> spacing disappears.
>>>>
>>>> Ian
>>>>> Hi Ian,
>>>>>
>>>>> The error message in the subject does appear that this is an issue that is related to Office 2003 Service Pack 3 when pasting named
>>>>> ranges from Excel.
>>>>>
>>>>> At present the workarounds that have bee reported include -
>>>>>
>>>>> 1. Use the cell range rather than a named range to pick and paste.
>>>>>
>>>>> 2. Similarly, once you have a working link in word if you press Alt+F9 to view field codes and edit the field code to use (add in)
>>>>> the named range then it also works.
>>>>>
>>>>> The additional item below, regarding character spacing isn't a variant I'd seen mentioned before. Are you saying the whole document
>>>>> prints out poorly with the linked item? What font and what printer are you using?
>>>>>
>>>>> ===========
>>>>> I'm having the same problem (as are others).
>>>>>
>>>>> I've also noticed that Excel sheets in Word 2003 SP3 linked to a named
>>>>> range print out poorly with unevenly spaced characters. As soon as the
>>>>> link is removed the printing is fine. In fact, if the link to a named
>>>>> range is replaced by a link to cell range, the problem of uneven
>>>>> spacing disappears.
>>>>>
>>>>> Ian>>
>>>>> --
>>>>>
>>>>> Bob Buckland ?:-)
>>>>> MS Office System Products MVP
>>>>>
>>>>> *Courtesy is not expensive and can pay big dividends*
>>>>>> Bob,
>>>>>> Does your first comment mean that it is not an office SP3 issue or is it
>>>>>> just that the subject does not indicate it is a Sp3 issue? The reason I ask,
>>>>>> is that on SP 2, you can paste an excel named range with no errors, but with
>>>>>> SP3 you get the error that is in the subject line.
>>>>>>
>>>>>> Using the cell range to do the paste is not acceptable. If a cell is moved,
>>>>>> the link breaks.
>>>>>>
>>>>>> Your second option is to un-name the cell, paste, name the cell and change
>>>>>> the link. I have close to 100 links in my document and I create one of these
>>>>>> documents a week. That would add a lot of time to my process and I get paid
>>>>>> by the job, not the hour.
>>>>>>
>>>>>> Is this being reconginzed as a bug and going to be corrected? I was just
>>>>>> about to port my company over to using the functionality instead of SET/REF
>>>>>> statements because it reduces writing time by about 10%, again this is per
>>>>>> week...
>>>>>>
>>>>>> for now, I would like to roll back to office SP2...
>>>>>>
>>>>>> --
>>>>>> KT
>>>>>>
>>>>>>
>>>>>> "Bob Buckland ?:-)" wrote:
>>>>>>> There are a lot of other posts starting to show up on this. This is a link
>>>>>>> one of the other users had found, but never had been able to complete it. It
>>>>>>> was not clear to me what to do as the registry keys and hives referenced did
>>>>>>> not exist and it did not say anything about having to add them.
>>>>>>>
>>>>>>> http://support.microsoft.com/default.aspx/kb/938815
>>>>>>>
>>>>>>> If this corrects the problem please respond with what was done.
>>>>>>>
>>>>>>> --
>>>>>>> KT
>>>>>>>
>>>>>>>
>>>>>>> "kt32707" wrote:
>>>>>>>> Re the character spacing irregularity, this occurs with a Kyocera
>>>>>>>> driver and a Microsoft driver for the Kyocera printer, and an HP
>>>>>>>> printer driver and Adobe Acrobat 7.0 pdf driver. I have tried
>>>>>>>> different fonts - Arial, Trebuchet, Times New Roman - to remedy the
>>>>>>>> problem without success.
>>>>>>>>
>>>>>>>> Like other posters, I feel the workarounds suggested are
>>>>>>>> unsatisfactory. Ironically my specific reason for upgrading to Office
>>>>>>>> 2003 was to improve linking performance, which was successful until
>>>>>>>> the SP3 update.
>>>>>>>>
>>>>>>>> Sorry about the delay in replying.
>>>>>>>>
>>>>>>>> Ian
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> On Nov 21, 8:15 pm, "Bob Buckland ?:-\)" <75214.226(At Beautiful
>>>>>>>> Downtown)compuserve.com> wrote:
>>>>>>>>> Well; here's some great news - upgrading to Office 2007 won't help. It too
>>>>>>>>> will not let you ember a named range - its just embeds the RC reference but
>>>>>>>>> not the name. I am desperate to find a solution to this (desperate to have
>>>>>>>>> wasted $400 on an upgrade!). Does anyone have a solution?
>>>>>>>>>
>>>>>>>>> Sean
>>>>>>>>>
>>>>>>>>>>> The problem here is obviously expecting Microsoft products to work the way they are supposed to.
>>>>>>>>>>>> On Tuesday, January 13, 2009 4:39 AM macropod wrote:
>>>>>>>>>>>> Hi Scott,
>>>>>>>>>>>>
>>>>>>>>>>>> Perhaps it is a user error - this NG is for application errors.