File Transfer - Certain item causes FTSEND to abort

Print Page | Close Window

Certain item causes FTSEND to abort

Printed From: Rocket Software
Category: AccuTerm Knowledge Base (read only)
Forum Name: File Transfer
Forum Description: Help with uploading & downloading database and document files
URL: https://forum.asent.com/forum_posts.asp?TID=2622
Printed Date: March 26 2026 at 5:07pm
Software Version: Web Wiz Forums 12.03 - http://www.webwizforums.com

Topic: Certain item causes FTSEND to abort

Posted By: sbhenkel
Subject: Certain item causes FTSEND to abort
Date Posted: April 20 2017 at 9:27am

I am trying to archive an old D3 file by using FTSEND to create text files on my pc for each D3 item. I am using "*" for the item list to get all items. It looks like it aborts when it encounters an item with a forward slash in the key. I earlier tried doing a similar file transfer using old routines that came with a ViaDuct terminal emulator. It aborted at the same spot.

Is the forward slash not allowed? If so, are there any other characters that aren't allowed? I know it would take a revision on your part to change the FTSEND to handle that character, or at least warn about it, but if I could get an idea of what characters aren't allowed I could at least move those out of the file or rename them before the transfer begins.

Replies:

Posted By: PSchellenbach
Date Posted: April 20 2017 at 11:14am

Hi Steve -

The problem is that you are using the D3 item-ID as the Windows file name. There are several characters that are illegal in Windows file names: / \ * < > ? " | : are the obvious ones. Instead of using '*' as the HOST.IDS argument, you could create an AM delimited list of the IDs, and a corresponding AM delimited list of target file names for the REMOTE.FILES argument, substituting the illegal characters when creating the REMOTE.FILES variable.

Thanks,

Pete

Posted By: sbhenkel
Date Posted: April 20 2017 at 12:00pm

That's a really good idea. However this file has too many items. I might be pushing things if I told it to assemble 2 dynamic arrays, each having over 500,000 elements in them. This time I guess I'll just have to select the ones that are "safe" and do them first. The do a select of the bad ones last and use your idea.