🚀 go-pugleaf

Michael--

I could have written:



myDocument.PageItems.Item(myCounter).Fit 1668247152 




But if I put the constants at the top of the script, I can move the script back to VB more easily, as I can simply comment out or delete those lines (rather than hunting down each instance of the number).

re: Differences between VB and VBScript

It's much easier to develop scripts in VB, because it's a full development environment: you can debug, view the object libraries, create user interfaces, etc. If your script requires more than a very simple user interface, you'll want to create an application using Visual Basic.

VBScripts, on the other hand, are easy to deploy--they're text files, and they can be embedded in HTML pages. While some Visual Basic applications might need an installer (depending on what/which controls you've used), all you need to run VBScripts is the Windows Scripting Host, which comes with all modern versions of Windows (and is also available for free download). It's often easier for me to post VBScripts here, and I sometimes do it when I know that the person asking for the script does not have the full version of VB.

There are also some language differences--a reasonably good overview is at: <http://msdn.microsoft.com/library/default.asp?url=/library/en-us/script56/html/vsgrpnonfeatures.asp> (this compares VBA to VBScript, but it's also relevant to VB to VBScript).

In general, I think VB is the way to go--it's *much* easier to develop scripts when you can debug, and all of the Scripting Guide examples are for VB, not VBScript. If you don't already have VB, you can download VB5 "Control Creation Edition" (CCE) for free from: <http://msdn.microsoft.com/vbasic/downloads/tools/cce/default.asp>

Hope this helps!

Thanks,

Ole