Hi,
Please keep your reply to the list !!!
You deprive others of the help you get if you send personal mail
in response to posts that help you with your requests.
On Monday, 18. September 2006 09:45, Andrej Ricnik-Bay wrote:
> On 9/18/06, Peter Marschall <[EMAIL PROTECTED]> wrote:
> > It's in line 118, where the Perl is told to perform the search() method
> > on something that is undefined nistead of an object of a class that
> > supports a search() method.
>
> OK, but I don't understand how or why.
>
> > > script1:
> > > package ldapcsv;
You still do work with packages !
> > > use strict;
> > > use Net::LDAP;
> > > use Net::LDAP::Entry;
> > > use Net::LDAP::Schema;
> > >
> > > sub search_it {
Why don't you do it the clean way:
pass the $ldap object as a parameter to search_it()
instead of relying on global variables, which is
a bad habit anyway.
> > > my ( $param ) = @_ ;
> > > print "<BR>In search_it: $param <BR>\n";
> > > $mesg = $ldap->search(
> >
> > I guess here is the problem.
> > Did you define $ldap in this package ?
>
> Yep. See above. I assumed that it might be a scope
> problem (and a timing issue) and put all three files into
> a single file, working without packaging. Even though
> my LDAP connect works fine, and I can bind, as soon
> as I attempt the search I get the same message (on a
> different line now, of course) - very confusing.
From what I can tell, the problem described is neither
a timing problem nor a problem of perl-ldap.
Peter
--
Peter Marschall
[EMAIL PROTECTED]
