Thanks for putting this in. I too had the same thought. 
   
   
  

Samantha Scott <[EMAIL PROTECTED]> wrote:
          I am curious how anyone would know what you use for FTP (or why they 
would care). I've had partners not allow browsing (no lists) on 
directories and they lock out certain types of FTP clients based on 
that behavior but a straight get/put...I just don't see why it makes 
a difference. If you are responsible for getting/putting the data 
then you should be able to use whatever tool you trust to do it.

I don't doubt that someone is trying to dictate this at all, mind 
you. I've seen enough similar behavior regarding other topics and I 
just don't understand it either. I find it annoying and insulting. 
I am an EDI professional capable of executing the required tasks and 
produce the proper results and if I fail to do so then I should be 
unemployed.

This is just a rant...I can't help because I use GIS for all my FTP. 
I just find it astounding and annoying that someone should try to 
dictate to you what tools you use. The only thing like that I can 
get behind is dictating that partners actually use a translator 
instead of getting some guy who knows nothing about EDI to code it by 
hand because it looks easy enough to him.

On Nov 1, 2006, at 7:44 PM, Brian Lehrhoff wrote:

> you can chuck gis and replace it with tx.
>
> using tx for just ftp processing is a perfectly good waste of a 
> mapping
> product.
>
> cute requires emanual to process. not a good choice.
>
> a perl compiler and a script would do the job very nicely and 
> reliably.
>
> Steve email wrote:
> > Has anyone ever integrated GIS with any of the
> > following 3rd party FTPs software solutions?
> >
> > Ascential Datastage TX
> > Cleo Lexicom
> > GlobalSCAPE Cute FTP Pro
> > IPSwitch WS FTP Pro
> > QualEDI for Windows
> > Trailblazer ZMOD FTP
> >
> > If so, would you give it any of these positive
> > recommendation? A very large trading parter of ours
> > requires that we use one of their approved FTPs
> > solutions from their list above. They don't want us
> > to use GIS to handle the FTPs communications with
> > them, so I'd like to select the one the works best
> > with GIS.
> >
> > So far I have not received any help from Sterling
> > support. Thank you for any comments.
> >
> > Steve Hung
> > [EMAIL PROTECTED]
> >
> >
> >
> >
> >
> >
> > __________________________________________________________
> > Low, Low, Low Rates! Check out Yahoo! Messenger's cheap PC-to- 
> Phone call rates
> > (http://voice.yahoo.com)
> >
> >
> >
> >
> > Yahoo! Groups Links
> >
> >
> >
> >
> >
> >
>
> -- 
> %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% 
> %%%%%%%%%
> Brian Lehrhoff, EA ([EMAIL PROTECTED])
> Messaging Consultant 201-913-4506
>
> Upgrade your Quickbooks for 20% off at http://www.brianlehrhoff.com
> Circular 230 Notice is located at http://www.brianlehrhoff.com/ 
> 230notice.html
> %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% 
> %%%%%%%%%
>
>
> 

[Non-text portions of this message have been removed]



         

 __________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

[Non-text portions of this message have been removed]



...
Please use the following Message Identifiers as your subject prefix: <SALES>, 
<JOBS>, <LIST>, <TECH>, <MISC>, <EVENT>, <OFF-TOPIC>

Job postings are welcome, but for job postings or requests for work: <JOBS> IS 
REQUIRED in the subject line as a prefix. 
Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/EDI-L/

<*> Your email settings:
    Individual Email | Traditional

<*> To change settings online go to:
    http://groups.yahoo.com/group/EDI-L/join
    (Yahoo! ID required)

<*> To change settings via email:
    mailto:[EMAIL PROTECTED] 
    mailto:[EMAIL PROTECTED]

<*> To unsubscribe from this group, send an email to:
    [EMAIL PROTECTED]

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/
 

Reply via email to