You will want to add 'use strict;' to the top of your code and turn on warnings using the -w command line flag or 'use warnings;'. This will help you pinpoint many syntactical and other errors. See here and here for why.

You're pretty much there with your existing code, a few slight adjustments should make it work: 

# the object name is actually SourceSafe.0
my $vss = Win32::OLE->new('SourceSafe.0');

# you must include the path and filename
# of the vss ini file you want, e.g.
# c:\data\sourcesafe\dev\srcsafe.ini
$vss->Open($srcsafe_ini, $user, $pwd);

# error checking
if (Win32::OLE->LastError() != 0)
{
    print 'Error: ', Win32::OLE->LastError();
}

[download]
If you're using the Activestate distribution, you should be able to use the HTML OLE Browser to see properties and methods available.

In reply to Re: PERL OLE connection to VSS by zakb
in thread PERL OLE connection to VSS by Anonymous Monk

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.