Re: Insert image to Excel programmatically

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Thanks Michael Harris.

I have another question here. If multiple pictures are going to be inserted
to the Excel ***, I face problem to arrange the pictures properly in
different rows since the size of the pictures is varying.

Anyway I can get the picture to fit into one cell so that the pictures won't
be overlapped? Currently the picture just spread across couple of cells
(vertically and horizontally) in the Excel *** and I have problem to
determine which is the next cell I should put the second picture and so and
so forth.

Hopefully I make my question clear. Thanks a lot



"Michael Harris (MVP)" wrote:

> LBT wrote:
> > Hi experts,
> >
> > I wish to insert JPEG files into the Excel document through
> > programming way. Is VBScript able to help me achieve my objective?
> > Please advice
> >
> > Thanks a lot!!!
>
> It so much easier to record a temp Excel macro while doing the task
> manually. Use the temp macro as a guide to create the VBScript
> equivalent...
>
> My vba vs. vbscript guide...
>
> Automating Office applications externally via VBScript (or any other COM
> capable language) starts by creating a reference to the specific Office
> application's Application object via CreateObject and the appropriate progid
> (e.g., "Word.Application" or "Excel.Application").
>
> Your best bet is to then refer to the Office VBA documentation...
>
> Documentation for Office object models is supplied with every copy of
> Office. Start the Office application you're interested in. On the menu bar,
> select Help/Contents and Index. In the contents, select Microsoft Visual
> Basic Reference/Visual Basic Reference. This will bring up the VBA help
> file.
>
> When you read the help on the various objects, properties, methods, etc. you
> have to keep in mind that it's written in the context of VBA hosted by a
> specific VBA-enabled application, not VBScript. VBA is hosted "from the
> inside" by the specific application. As the host, it automatically provides
> things to the VBA code that aren't automatic when you automate an
> application's object model "from the outside" using VBScript hosted by WSH.
>
> The key items to remember:
>
> --- No objects are automatically exposed to VBScript. You generally use an
> explicit CreateObject to get an instance of an object to use as the "root",
> usually the ".Application" object.
>
> ---In VBA that Application object and it's immediate interface members
> (properties/methods) are automatically exposed. In VBScript you refer to the
> Application object and it's properties/methods through the object variable
> reference returned by the CreateObject.
>
> ---Named constants specific to the application aren't exposed. You can
> either look them up and code them locally in the VBScript code as Const
> variables, or you can use the .wsf file format and a <reference> element to
> automatically expose them.
>
> ---VBA supports named argument syntax (e.g., ArgName:="argvalue") in method
> calls. In WSH hosted VBScript, you have to code all arguments as positional
> arguments since named argument syntax is not supported.
>
> Once you understand the "VBA from the inside" vs "VBScript from the outside"
> issues and the fundamental differences between VBA and VBScript as separate
> but similar languages, you should be able to mentally "port" VBA and even
> full VB examples to VBScript.
>
> A common trick scripters often use is recording a VBA macro within an Office
> application while performing a task that they want to automate and then
> porting the VBA macro code to VBScript.
>
>
> --
> Michael Harris
> Microsoft MVP Scripting
>
>
>
>
>
.

Quantcast