Article View: adobe.scripting.indesign
Article #15860CS behaving differently
From: Mike_Mepham
Date: Sun, 09 Nov 2003 00:28
Date: Sun, 09 Nov 2003 00:28
13 lines
1718 bytes
1718 bytes
Over the past year or so I have built up a library of scripts that handle very specific jobs for me. I anticipated some problems on the upgrade to CS, but I'm finding that some of my scripts simply will not work at all. An example: many of my newspaper jobs are modular in format and I have created ID "form" documents that simply contain a number of files that are relinked to new files according to date. A script displays a list of links in the document, creates a list of new filenames by date for those links that I choose and then relinks to the new files and updates the document. This has worked perfectly for over a year, but now I find that I get a VB error "Object does not support this property or method" on MyLinkItem.Relink MyNewPath where MyLinkItem was set to MyLinks.Item(n) in a for/next loop. If not a path or filename, what property would a Relink support now? Obviously I'm keen to get this one sorted out, but of greater concern is the fact that none of my scripts are working at first try. Am I in for a complete change of the way that ID scripting has worked up to now? Mike
Technical Details
Message-ID:
<2cce49b9.-1@webx.la2eafNXanI>Path:
arc1-ca.pugleaf.net!archiver1.google.com!news2.google.com!news.maxwell.syr.edu!eusc.inter.net!newsfeed01.sul.t-online.de!t-online.de!webxShow Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: f939a,1b7bd4d38ede4edd,start X-Google-Attributes: gidf939a,public X-Google-ArrivalTime: 2003-11-08 16:37:44 PST From: Mike_Mepham@adobeforums.com Path: arc1-ca.pugleaf.net!archiver1.google.com!news2.google.com!news.maxwell.syr.edu!eusc.inter.net!newsfeed01.sul.t-online.de!t-online.de!webx Newsgroups: adobe.scripting.indesign Subject: CS behaving differently Message-ID: <2cce49b9.-1@webx.la2eafNXanI> Date: Sat, 8 Nov 2003 16:28:43 -0800 Lines: 24 MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 8bit