What happens when you only have access to commercial software like SSH's Tectia software and the developer decides to not implement a proper scp implementation because they have their own proprietary standard call SFTP?

Figure out how scp works and do it old school.  Basically scp is a wrapper around an SSH session which results in piping a file to or from a server.  Unfortunate for scp users is the documentation is considered to be the source-code for the scp clients and servers.

So what do you do if need to get a file that's up on an SSH server and scp is either not there or broken by your omnipotent software vendor?  Follow these steps and you'll have a working scp without scp.

First off thanks to Jan Pechanec's weblog:
how_the_scp_protocol_works
and the kind people at OpenSSH:
browse_Openbsd_CVS_scp.c

These instr

Instructions have been tested on RHEL and should work on other *nix systems.  Putty in 
Windows works as noted:
1.  To pull a file from the server:
Linux
ssh account@server.com 'scp -f somefile.txt' > somefile.txt
enter the password if prompted
Then hit <CTRL><SHIFT>@ (a good number is 7 times) and hit enter

Windows
plink account@server.com "scp -f somefile.txt" >somefile.txt
enter a password (PLINK won't display a password prompt when using the '>' pipe)
Then hit <CTRL><SHIFT>@ (a good number is 7 times) and hit enter

You should now have a file sitting on you system in your current directory.  If something doesn't work the way you expect it drop the > somefile.txt from the command and try again.

Uploading a file to the server is a little more involved as the server needs to know how many characters are in the file being uploaded.
On Linux run:
wc -c somefile.txt and note the number of characters
Then run:
ssh account@server.com 'scp -t somefile.txt'
enter the password when prompted
then enter:
C0644 the_number_of_characters somefile.txt

Next paste the contents of the file to be uploaded and hit enter

and finish up with:
e

You should now be back to your command prompt