EsFtp - ActiveX Control

Eurosource, Gruvbyn 415, S-820 50 LOOS, Sweden
(akhe@eurosource.se) (http://www.eurosource.se)
Updated: 1999-05-05 21:42

With this control you can handle all aspects of the client side part of the ftp-protocols. Unlike many other products on the market this control is built from the ground up and is not dependent on any OS dll's except for the MFC runtime libraries. EsFtp can move files from a client to a server or vice versa. The control can delete libraries or files on the server.

 


 

Installation

Transfer EsFtp32.ocx to your \windows\system or \winnt35\system32 directory and register it by executing the command:

RegSvr32 \Windows\System\EsFtp32.ocx

RegSvr32.exe can be found on the Visual Basic 4.0 CD-ROM and in our dll archive (www.eurosource.se). If RegSvr32.exe fails, it's probably because you don't have the MFC 4.0 DLL library installed on your system. This is available from many sources on the Internet including our ftp archive as MFCDLLS.ZIP. Regsvr32.exe is also included in this archive. If you want to check if you already got the files in mfcdlls.zip they are

  • mfc42.dll
  • msvcrt40.dll
  • oc30.dll
  • olepro32.dll
  • regsvr32.exe

 

Cookbook or how to use the EsFtp Control

Create a EsFtp object for an ASP application

Use the object ID ESFTP.EsFtpCtrl.1 when you create an instance of the EsFtpCtrl.

So the code

<object RUNAT="server" PROGID="ESFTP.EsFtpCtrl.1" id="EsCRC"> </object>
or
set EsCRC = server.CreateObject("EsCRC.EsCRCCtrl.1")

will create the object for you.

Connecting to an ftp-server

Use the following code to start a session with an ftp server. There is no need to set the port in code as this already is the default value but it is shown here for completeness. The lblStatus is just a text label on the form that gives the user some information about what is going on.

Screen.MousePointer = 11
lblStatus = "Working......"
DoEvents
EsFtp1.Port = 21    ' Is already set to 21
EsFtp1.RemoteHost = "ftp.somewhere.com"
EsFtp1.UserName = "anonymous"
EsFtp1.Password = "john.doe@somewhere.com"
If EsFtp1.Connect Then
    lblStatus = "Connected"
Else
    lblStatus = "Connect Failed"
End If
Screen.MousePointer = 0

Get the directory contents of a remote server

In this code fragment we retrive the remote directory structure when a button is clicked. When the button is clicked the cmdGetRemoteDir_Click() subroutine gets called. This routine clears two listboxes, ListDirs which is used for drectories and ListFiles which is used for files. I also add the "current directory" and "up an level" tokens in the directory listbox.

The call to the GetRemoteDirFile method get a file containing the directory structure as its return value. If this is a file have a valid path in it you have the directory structure in that file if not some error have occured.

You can parse this file yourself for information about the returned directory or you can use the DirectoryLine event which is a convenient way to interpret the directory content.

Private Sub cmdGetRemoteDir_Click()
    Dim filename As String
    Screen.MousePointer = 11
    lblStatus = "Working......"
    DoEvents
    ListDirs.Clear
    ListFiles.Clear
    ListDirs.AddItem "."
    ListDirs.AddItem ".."
    filename = EsFtp1.GetRemoteDirFile
    If Len(filename) > 0 Then
        lblStatus = "Temporary file is " + filename
    Else
        lblStatus = "Problems! No dir file retrived"
    End If
    Screen.MousePointer = 0
End Sub

This sub is hooked to the DirectoryLine event which is called ones for every directory line returned from the server. In this subroutine we just fill directories names in the directory listbox and filenames in the filenames listbox.

Private Sub EsFtp1_DirectoryLine(ByVal fDir As Boolean, ByVal Name As      String, ByVal Size As Long)
    If fDir = True Then
        ListDirs.AddItem Name '+ " " + Str(Size)
    Else
        ListFiles.AddItem Name '+ " " + Str(Size)
    End If
End Sub

 


 


Properties

 


 

BOOL bExtractDate

Normally DirectoryLine events are fired when a directory is fetched. If you set this flag to true DirectoryLineEx events is fired instead. This event also give the date information.

 


 

long ErrorNo

Read only.

Holds the last generated error-code. If you get a False return value form a method you should always check the ErrorNo property to determine the cause for the error.

There are two types of error messages. One type is the ftp reply codes and one is the WinSock error codes.

Ftp reply codes

-1 General Error.

WinSock error codes

10013 - WSAEACCES, Permission denied.
An attempt was made to access a socket in a way forbidden by its access permissions. An example is using a broadcast address for sendto without broadcast permission being set using setsockopt(SO_BROADCAST).

10048 - WSAEADDRINUSE, Address already in use.
Only one usage of each socket address (protocol/IP address/port) is normally permitted. This error occurs if an application attempts to bind a socket to an IP address/port that has already been used for an existing socket, or a socket that wasn't closed properly, or one that is still in the process of closing. For server applications that need to bind multiple sockets to the same port number, consider using setsockopt(SO_REUSEADDR). Client applications usually need not call bind at all - connect will choose an unused port automatically.

10049 - WSAEADDRNOTAVAIL, Cannot assign requested address.
The requested address is not valid in its context. Normally results from an attempt to bind to an address that is not valid for the local machine, or connect/sendto an address or port that is not valid for a remote machine (e.g. port 0).

10047 - WSAEAFNOSUPPORT, Address family not supported by protocol family.
An address incompatible with the requested protocol was used. All sockets are created with an associated "address family" (i.e. AF_INET for Internet Protocols) and a generic protocol type (i.e. SOCK_STREAM). This error will be returned if an incorrect protocol is explicitly requested in the socket call, or if an address of the wrong family is used for a socket, e.g. in sendto.

10037 - WSAEALREADY, Operation already in progress.
An operation was attempted on a non-blocking socket that already had an operation in progress - i.e. calling connect a second time on a non-blocking socket that is already connecting, or canceling an asynchronous request (WSAAsyncGetXbyY) that has already been canceled or completed.

10053 - WSAECONNABORTED, Software caused connection abort. 
An established connection was aborted by the software in your host machine, possibly due to a data transmission timeout or protocol error.

10061 - WSAECONNREFUSED, Connection refused.
No connection could be made because the target machine actively refused it. This usually results from trying to connect to a service that is inactive on the foreign host - i.e. one with no server application running.

10054 - WSAECONNRESET, Connection reset by peer.
A existing connection was forcibly closed by the remote host. This normally results if the peer application on the remote host is suddenly stopped, the host is rebooted, or the remote host used a "hard close" (see setsockopt for more information on the SO_LINGER option on the remote socket.)

10039 - WSAEDESTADDRREQ, Destination address required.
A required address was omitted from an operation on a socket. For example, this error will be returned if sendto is called with the remote address of ADDR_ANY.

10014 - WSAEFAULT, Bad address.
The system detected an invalid pointer address in attempting to use a pointer argument of a call. This error occurs if an application passes an invalid pointer value, or if the length of the buffer is too small. For instance, if the length of an argument which is a struct sockaddr is smaller than sizeof(struct sockaddr).

10064 - WSAEHOSTDOWN, Host is down.
A socket operation failed because the destination host was down. A socket operation encountered a dead host. Networking activity on the local host has not been initiated. These conditions are more likely to be indicated by the error WSAETIMEDOUT.

10065 - WSAEHOSTUNREACH, No route to host.
A socket operation was attempted to an unreachable host. See WSAENETUNREACH

10036 - WSAEINPROGRESS, Operation now in progress.
A blocking operation is currently executing. Windows Sockets only allows a single blocking operation to be outstanding per task (or thread), and if any other function call is made (whether or not it references that or any other socket) the function fails with the WSAEINPROGRESS error.

10004 - WSAEINTR, Interrupted function call.
A blocking operation was interrupted by a call to WSACancelBlockingCall.

10022 - WSAEINVAL, Invalid argument.
Some invalid argument was supplied (for example, specifying an invalid level to the setsockopt function). In some instances, it also refers to the current state of the socket - for instance, calling accept on a socket that is not listening.

10056 - WSAEISCONN, Socket is already connected.
A connect request was made on an already connected socket. Some implementations also return this error if sendto is called on a connected SOCK_DGRAM socket (For SOCK_STREAM sockets, the to parameter in sendto is ignored), although other implementations treat this as a legal occurrence.

10024 - WSAEMFILE, Too many open files.
Too many open sockets. Each implementation may have a maximum number of socket handles available, either globally, per process or per thread.

10040 - WSAEMSGSIZE, Message too long.
A message sent on a datagram socket was larger than the internal message buffer or some other network limit, or the buffer used to receive a datagram into was smaller than the datagram itself.

10050 - WSAENETDOWN, Network is down. 
A socket operation encountered a dead network. This could indicate a serious failure of the network system (i.e. the protocol stack that the WinSock DLL runs over), the network interface, or the local network itself.

10052 - WSAENETRESET, Network dropped connection on reset.
The host you were connected to crashed and rebooted. May also be returned by setsockopt if an attempt is made to set SO_KEEPALIVE on a connection that has already failed.

10051 - WSAENETUNREACH, Network is unreachable. 
A socket operation was attempted to an unreachable network. This usually means the local software knows no route to reach the remote host.

10055 - WSAENOBUFS, No buffer space available.
An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full.

10042 - WSAENOPROTOOPT, Bad protocol option.
An unknown, invalid or unsupported option or level was specified in a getsockopt or setsockopt call.

10057 - WSAENOTCONN, Socket is not connected.
A request to send or receive data was disallowed because the socket is not connected and (when sending on a datagram socket using sendto) no address was supplied. Any other type of operation might also return this error - for example, setsockopt setting SO_KEEPALIVE if the connection has been reset.

10038 - WSAENOTSOCK, Socket operation on non-socket.
An operation was attempted on something that is not a socket. Either the socket handle parameter did not reference a valid socket, or for select, a member of an fd_set was not valid.

10045 - WSAEOPNOTSUPP, Operation not supported.
The attempted operation is not supported for the type of object referenced. Usually this occurs when a socket descriptor to a socket that cannot support this operation, for example, trying to accept a connection on a datagram socket.

10046 - WSAEPFNOSUPPORT, Protocol family not supported.
The protocol family has not been configured into the system or no implementation for it exists. Has a slightly different meaning to WSAEAFNOSUPPORT, but is interchangeable in most cases, and all Windows Sockets functions that return one of these specify WSAEAFNOSUPPORT.

10067 - WSAEPROCLIM, Too many processes.
A Windows Sockets implementation may have a limit on the number of applications that may use it simultaneously. WSAStartup may fail with this error if the limit has been reached.

10043 - WSAEPROTONOSUPPORT, Protocol not supported. 
The requested protocol has not been configured into the system, or no implementation for it exists. For example, a socket call requests a SOCK_DGRAM socket, but specifies a stream protocol.

10041 - WSAEPROTOTYPE, Protocol wrong type for socket.
A protocol was specified in the socket function call that does not support the semantics of the socket type requested. For example, the ARPA Internet UDP protocol cannot be specified with a socket type of SOCK_STREAM.

10058 - WSAESHUTDOWN, Cannot send after socket shutdown.
A request to send or receive data was disallowed because the socket had already been shut down in that direction with a previous shutdown call. By calling shutdown a partial close of a socket is requested, which is a signal that sending or receiving or both has been discontinued.

10044 - WSAESOCKTNOSUPPORT, Socket type not supported.
The support for the specified socket type does not exist in this address family. For example, the optional type SOCK_RAW might be selected in a socket call, and the implementation does not support SOCK_RAW sockets at all.

10060 - WSAETIMEDOUT, Connection timed out.
A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.

10035 - WSAEWOULDBLOCK, Resource temporarily unavailable.
This error is returned from operations on non-blocking sockets that cannot be completed immediately, for example recv when no data is queued to be read from the socket. It is a non-fatal error, and the operation should be retried later. It is normal for WSAEWOULDBLOCK to be reported as the result from calling connect on a non-blocking SOCK_STREAM socket, since some time must elapse for the connection to be established.

11001 - WSAHOST_NOT_FOUND, Host not found.
No such host is known. The name is not an official hostname or alias, or it cannot be found in the database(s) being queried. This error may also be returned for protocol and service queries, and means the specified name could not be found in the relevant database.

(OS dependent) - WSA_INVALID_HANDLE, Specified event object handle is invalid.
An application attempts to use an event object, but the specified handle is not valid.

(OS dependent) - WSA_INVALID_PARAMETER, One or more parameters are invalid.
An application used a Windows Sockets function which directly maps to a Win32 function. The Win32 function is indicating a problem with one or more parameters.

(OS dependent) - WSAINVALIDPROCTABLE, Invalid procedure table from service provider.
A service provider returned a bogus proc table to WS2_32.DLL. (Usually caused by one or more of the function pointers being NULL.)

(OS dependent) - WSAINVALIDPROVIDER, Invalid service provider version number.
A service provider returned a version number other than 2.0.

(OS dependent) - WSA_IO_PENDING, Overlapped operations will complete later.
The application has initiated an overlapped operation which cannot be completed immediately. A completion indication will be given at a later time when the operation has been completed.

(OS dependent) - WSA_IO_INCOMPLETE, Overlapped I/O event object not in signaled state.
The application has tried to determine the status of an overlapped operation which is not yet completed. Applications that use WSAWaitForMultipleEvents in a polling mode to determine when an overlapped operation has completed will get this error code until the operation is complete.

(OS dependent) - WSA_NOT_ENOUGH_MEMORY, Insufficient memory available.
An application used a Windows Sockets function which directly maps to a Win32 function. The Win32 function is indicating a lack of required memory resources.

10093 - WSANOTINITIALISED, Successful WSAStartup not yet performed.
Either the application hasn’t called WSAStartup or WSAStartup failed. The application may be accessing a socket which the current active task does not own (i.e. trying to share a socket between tasks), or WSACleanup has been called too many times.

11004 - WSANO_DATA, Valid name, no data record of requested type.
The requested name is valid and was found in the database, but it does not have the correct associated data being resolved for. The usual example for this is a hostname -> address translation attempt (using gethostbyname or WSAAsyncGetHostByName) which uses the DNS (Domain Name Server), and an MX record is returned but no A record - indicating the host itself exists, but is not directly reachable.

11003 - WSANO_RECOVERY, This is a non-recoverable error.
This indicates some sort of non-recoverable error occurred during a database lookup. This may be because the database files (e.g. BSD-compatible HOSTS, SERVICES or PROTOCOLS files) could not be found, or a DNS request was returned by the server with a severe error.

(OS dependent) - WSAPROVIDERFAILEDINIT, Unable to initialize a service provider.
Either a service provider's DLL could not be loaded (LoadLibrary failed) or the provider's WSPStartup/NSPStartup function failed.

(OS dependent) - WSASYSCALLFAILURE, System call failure. 
Returned when a system call that should never fail does. For example, if a call to WaitForMultipleObjects fails or one of the registry functions fails trying to manipulate theprotocol/namespace catalogs.

10091 - WSASYSNOTREADY, Network subsystem is unavailable.
This error is returned by WSAStartup if the Windows Sockets implementation cannot function at this time because the underlying system it uses to provide network services is currently unavailable. Users should check:

that the appropriate Windows Sockets DLL file is in the current path,

that they are not trying to use more than one Windows Sockets implementation simultaneously. If there is more than one WINSOCK DLL on your system, be sure the first one in the path is appropriate for the network subsystem currently loaded.

the Windows Sockets implementation documentation to be sure all necessary components are currently installed and configured correctly.

11002 - WSATRY_AGAIN, Non-authoritative host not found.
This is usually a temporary error during hostname resolution and means that the local server did not receive a response from an authoritative server. A retry at some time later may be successful.

10092 - WSAVERNOTSUPPORTED, WINSOCK.DLL version out of range.
The current Windows Sockets implementation does not support the Windows Sockets specification version requested by the application. Check that no old Windows Sockets DLL files are being accessed.

10094 - WSAEDISCON, Graceful shutdown in progress.
Returned by recv, WSARecv to indicate the remote party has initiated a graceful shutdown sequence.

(OS dependent) - WSA_OPERATION_ABORTED, Overlapped operation aborted.
An overlapped operation was canceled due to the closure of the socket, or the execution of the SIO_FLUSH command in WSAIoctl.

 


short HostType

This is an enumerated property that holds the host type of the remote host. The default is HOST_AUTO which determines the host type automatically.

 


 

BSTR LocalDir

The local directory is a directory on the client machine. Set this to the path of the directory you want to download files to or upload files from.

 


 

LPSTR Password

The password used to establish an ftp-session to a specified server for the connecting user..

 


 

long Port

The port that should be used. Normally this is 21 (the standard ftp port).

 


 

BSTR RemoteDir

A directory on the remote machine. Set this property to the path on the remote machine where you want to work.

 


 

BSTR RemoteHost

This is either the name (ftp.somewhere.com) or the IP-address (192.128.0.1) of the remote machine to which you want to do a ftp-connection.

 


 

long Timeout

This is the Time-out, in milliseconds, used when receiving/sending data from/to the ftp-server.

 


 

BSTR UserName

This is the username on the remote machine for the connecting user.

 


 

BOOL fUnique

Set to true if you want to make certain that no files are beeing overwitten during download.

 


 

BOOL fUseFirewall

This property have no meaning at the moment.

 


Methods


 

BOOL ChangeWorkingDir(LPCTSTR Path)

With this method you can change the working directory on the remote server. Just call the method with the remote-path as the only paameter.

If the function return true everything is OK otherwise you should check the ErrorNo property to get the cause for the failure.

 


 

BOOL Connect()

Start a ftp-session with a remote host. You should first set the desired username in the UserName property, the password in the Password property and the remote hostname in the Remotehost property.

If the function return true everything is OK otherwise you should check the ErrorNo property to get the cause for the failure.

 


 

BOOL DeleteFile( LPCTSTR path )

This is an alias for RemoveFile.

 


 

BOOL Disconnect()

Call this method to terminate a ftp-session. If the function return true everything is OK otherwise you should check the ErrorNo property to get the cause for the failure.

 


 

BSTR GetRemoteDirFile()

With this function you retrive the content of the current directory on the remote server. You use code like the following to accomblish this

    Dim filename as string

    filename = EsFtp1.GetRemoteDirFile
    If Len(filename) > 0 Then
        lblStatus = "Temporary file is " + filename
    Else
        lblStatus = "Problems! No dir file retrived"
    End If

A  temporary file is received which holds the actual directory structure. If an error occurs a null length filename is returned indicating failure. In that case you should check the ErrorNo property to get the cause for the failure.

You can now parse the returned file or take advantage of the DirectoryLine event which gives this information parsed for you.

 


 

BOOL GetRemoteFile(LPCTSTR RemoteName, LPCTSTR LocalName, LPCTSTR Type)

Use this method to receive a file from the remote server. The RemoteName is the name of the file on the remote machine. The LocalName is the name you want for the file on your local machine. If this parameter is set to an empty string the RemoteName is used. Type can be one of the following

  • Type = "I" - the file is a binary file.
  • Type="A" - the file is an ASCII file.

If the function return true everything is OK otherwise you should check the ErrorNo property to get the cause for the failure.

 


 

BSTR GetWorkingDir()

Use thsi method to get the current working directory on the remote server.

 


 

BOOL MakeDir(LPCTSTR path)

Use this to create a directory on the remote server. The path parameter holds the name of the directory.

If the function return true everything is OK otherwise you should check the ErrorNo property to get the cause for the failure.

 


 

BOOL MkDir(LPCTSTR path)

This is an alias for MakeDir.

 


 

short Quote(LPCTSTR CmdString)

With this command you can send a command of your choice to the ftp-server. Just supply your command with any possible parameters in the CmdString parameter.

 


 

BOOL RenameFile(LPCTSTR oldname, LPCTSTR newname)

With this command you can rename a file on the remote server.

If the function return true everything is OK otherwise you should check the ErrorNo property to get the cause for the failure.


 

BOOL RemoveDir(LPCTSTR Path)

Use this method to delete a directory on the remote server. The Path parameter holds the name of the directory.

If the function return true everything is OK otherwise you should check the ErrorNo property to get the cause for the failure.

 


 

BOOL RemoveDir(LPCTSTR Path)

Use this method to delete a directory on the remote server. The Path parameter holds the name of the directory.

If the function return true everything is OK otherwise you should check the ErrorNo property to get the cause for the failure.

 


 

BOOL RemoveDirAndFiles(LPCTSTR Path)

Use this method to delete a directory and the files in that directory on the remote server. The Path parameter holds the name of the file to delete. The method fails if the directory contains other folders.

If the function return true everything is OK otherwise you should check the ErrorNo property to get the cause for the failure.

 


 

BOOL RemoveFile(LPCTSTR Path)

Use this method to delete a file on the remote server. The Path parameter holds the name of the file.

If the function return true everything is OK otherwise you should check the ErrorNo property to get the cause for the failure.

 


 

BOOL RmDir(LPCTSTR Path)

This is an alias for RemoveDir.

 


 

BOOL SendLocalFile(LPCTSTR LocalName, LPCTSTR RemoteName, LPCTSTR Type)

Use this method to trensfere a file to a remote ftp-server. The LocalName parameter holds the name of the file to transfere. RemoteName holds the name for the file on the remote server or an empty string if this is the same name as in the LocalName parameter. The type indicates the type of file

  • Type = "I" - the file is a binary file.
  • Type="A" - the file is an ASCII file.

If the function return true everything is OK otherwise you should check the ErrorNo property to get the cause for the failure.

 


Events

 


 

DirectoryLine( BOOL fDir, LPCTSTR Name, long Size )

This event is called ones for each line in a directory structure returned after a call to the GetRemoteDirFile method. The fDir parameter is set to true if the line represents a directory. The Name parameter is the directory/file name and the Size is the size (in bytes) for the file.

If you want to fill information in listboxes you can use code as the following. ListDirs is a listbox holding directory information and ListFiles is a listbox holding file information.

Private Sub EsFtp1_DirectoryLine(ByVal fDir As Boolean, ByVal Name As      String, ByVal Size As Long)
    If fDir = True Then
        ListDirs.AddItem Name '+ " " + Str(Size)
    Else
        ListFiles.AddItem Name '+ " " + Str(Size)
    End If
End Sub

 


 

DirectoryLineEx( BOOL fDir, LPCTSTR Name, long Size, LPCTSTR DateStr )

This event is fired instead of DirectoryLine if the bExtractDate property is set to true. This event also gives the date for the directory item.

 


 

Response( short Code, LPCTSTR Message )

Every response from an ftp-server is reported in this event. The actual message is in the Message parameter and the code parameter is the numeric interpretion. You can use this event to interpret the outcome after you issue a command or just as a way to report error/success information to the user.

 


 

Status (short Mtype, long progress)

Certain operations take some time to complete. This event gives you information about how much of the job that has been completed. When a lengthy job starts the status event is fired with progress set to 0 and then you get status events until the job is complete and a status event with progress set to 100 is fired. You therefore only need to write the progress to a gauge control to give your users dynamic information.

The Mtype parameter have tree possible values

  • MType = 0 - Starting transfere. If progress =-1 the filesize is unknown.
  • MType = 1 - Progress holds valid info about the transfere state. This is only true if MType has been received with a value of 0 and progress set to 0. If this is not the case you have to disregard this event.
  • MType = 2 - The transfer completed.

You can use code as the following to give the user info about the progress of a transefer

Private Sub EsFtp1_Status(ByVal MType As Integer, ByVal Progress As Long)
    If (MType = 0) Then
        ' Start of transfer
        If (Progress = -1) Then
            ' No file size available
            fProgress = False
        Else
            fProgress = True
            ProgressBar1.Max = Progress
        End If
    ElseIf (MType = 1) Then
        ' Transfer in progress
        If (fProgress) Then
            ProgressBar1.Value = Progress
        End If
    ElseIf (MType = 2) Then
        ' End of transfer
        lblStatus = "File received OK!"
        ' No Progress as default
        fProgress = False
    End If
End Sub

 


 

 

Additional Documentation

 

Where to get the control?

It is possible that you are reading this documentation without having access to the control itself. If you have Internet access you just need to connect to http://www.eurosource.se and fetch a fully working sample of the control. At this location you can also find samples on how to use the control.

We can email the control anywhere in the world if you send us a request to do so. Please state if you want MIME or BINHEX coding. Send request to sales@eurosource.se

If you use the unregistered version of the control a splash screen is displayed from time to time reminding you to register.To get rid of this nag-screen you need to register. Information is available at our site.

We ship anywhere in the world with World-wide First Class/Airmail if you select this option. The only media supported is 3.5" diskettes.The charge for this type of delivery is $15 (USD) extra.

Support

You can get support by sending email to support@eurosource.se. You can also find relevant information on-line at http://www.eurosource.se

We also check the newsgroup comp.lang.basic.visual.3rdparty on a regular basis and will try to help on all questions posted there.

 


 

How to contact us

  • If you need to contact us the preferred way is through email. Please send a mail to info@eurosource.se
  • If you want to use phone please call us at +46 657 10620 and Fax: +46 657 10612.
  • If you want to send a snailmail you can send it to
  • Eurosource, Gruvbyn 415A, S-820 50 LOOS, SWEDEN