> > [Ted suggested disabling anti-virus]
That didn't work. However, it prompted me to actually look at my error
logs. Sometimes I forget that I have a logging feature.
In Windows 7 the error definitely occurs on .documents.Add (or
.documents.Add(), or documents.Add(cSomePathSomeFile).
However, in XP, using the original code in a compiled .exe (anti-virus on
or off makes no difference):
FCREATE(cSomePathSomeFile)
WITH oWord
.documents.Add
.
.
etc.
ENDWITH
The process manages to insert one block of text from the FRX Title band
into the Word document, and is working on the second when it encounters a
call to:
oDocShapes.AddPicture( [bunch of parms] )
and fails with "This is not a valid file name."
Now, it got through an .AddPicture() call previously to get the first
textblock done. It's not literally trying to place a real image file into
the document; it's just essentially pasting blocks of text from FRX report
labels into the Word document. And again, this code works without error in
Win 2000, and it's not my code. So I haven't fully investigated what is
being passed to AddPicture--but it seems to me that I can't fix it if it's
going to behave in such an arbitrary fashion.
Does this ring a bell with anyone?
Thanks for all the help!
Ken Dibble
www.stic-cil.org
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message:
http://leafe.com/archives/byMID/profox/[email protected]
** All postings, unless explicitly stated otherwise, are the opinions of the
author, and do not constitute legal or medical advice. This statement is added
to the messages for those lawyers who are too stupid to see the obvious.
