Using INCLUDEPICTURE, I suspect the only sensible way to solve these
problems will be to merge to a new document and run some VBA that
a. unlinks the INCLUDEPICTURE fields (i.e. does what you're doing with
ctrl-shift-F9
b. examines all the graphic objects inserted using INCLUDEPICTURE and
adjusts their width and height to be 100% of the original where they are
currently > 100%, and leaves them if they are < 100%. Or something along
those lines.
I don't have code for that.
If you are including images that are fairly static - i.e. the set of images
does not change much each time you merge, and you are willing to modify your
set of images pre-merge, you could consider putting all the images you need
into another Word document, adjusting their sizes, and bookmarking each one
as imagen (image1, image2,...) so that you can include them using a nested
INCLUDETEXT, e.g. something like
{ INCLUDETEXT "c:\\myimages\\myimages.doc" "image{ MERGEFIELD imageno }" }
I haven't tried it but that would probably be my starting point. Useless of
course if Ratinal Soda is dynamically maintaining/exporting images as your
specs. change.
Just my 2c-worth,
Peter Jamieson
> Hi
> I use Rational Soda to generate functional specs with included images.
[quoted text clipped - 27 lines]
>
> Thanks in advance
th bean - 26 May 2006 22:35 GMT
Thanks Peter
A cunning solution and yes, I can do that.
Although it is not a pretty solution, because of the limitation of the
includepicture command, it is the only one I can see will work. The images
are static but there are a lot of them..... c'est la vie.
Again, thanks heaps
> Using INCLUDEPICTURE, I suspect the only sensible way to solve these
> problems will be to merge to a new document and run some VBA that
[quoted text clipped - 55 lines]
> >
> > Thanks in advance