Unless you explicitly share a varible, each thread will have it's own copy.

But, if you assign an object to a variable, before you spawn a thread, the new thread will usually not be able to use its copy successfully. It is quite hard to advise you without seeing your code.

I have 2 files

1. Package wrapper for NET::FTP (error checking)
2. main code that creates threads and self master.
<code>
# File 1
package myFtp;
use Net::FTP;
use Net::Cmd;
our @ftpObj;
our @ftpList = ();
our @code;

sub Connect
{
    my ($ftpServer, $ftpTimeout, $connection_type) = @_;

    #debug ("Trying -> ", $ftpServer);
    $ftpObj = Net::FTP->new($ftpServer, Timeout => $ftpTimeout, Passiv
+e => $connection_type);
    return;
}
#other functions....
[download]

#File 2 (Main Code)
use SPFtp qw(/^\$/);
use SPFtp qw (Connect Login PrepareLsFtpList deleteFile GetFile GetFil
+eSize Logout GetMessage CheckConnection);

# Create Thread 1
Connect("bugs", "60", "binary");
# Create Thread 2
Connect("bugs", "60", "binary");
# Create Thread 3
Connect("bugs", "60", "binary");
# Create Thread 4
Connect("bugs", "60", "binary");
# Master Thread
[download]

Here is my question?

Will $ftpObj Variable get screwed up? I am pretty sure it will.

Hm. You declare our @ftpObj;; you then assign to $ftpObj = ...;; you post a 'trace', but don't show any code that produces that trace.

Here is my question?

Will $ftpObj Variable get screwed up? I am pretty sure it will.

Then don't do that!

Stop wasting my ....... time!