Jump to content

Fabian

Members
  • Content Count

    8
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Fabian

  • Rank
    member

Profile Information

  • Industry
    Printing
  • Location
    Sweden

FileMaker Experience

  • Skill Level
    Intermediate
  • FM Application
    18

Platform Environment

  • OS Platform
    Mac
  • OS Version
    High Sierra

FileMaker Partner

  • Certification
    Not Certified

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. My users like using a FTP client as they can upload files "in the background" and keep working in FM. When I want them to upload the files straight through FM, I get compliance issues because of this (files could be 500Mb). If the file is already on the FMS I do PSoS, but when it's on the client desktop using FM will block them from working in FM during upload. Is there a good way to achieve uploading from the client in the background, without blocking FM?
  2. Yes, so I can't see any use at all for this function, as I would typically use it to check I'm still connected before I upload or change directory (I think this is from your sample file). Thanks for the suggestion. That is how I do it when the team sends a file from FM and then I show them a dialogue box to confirm if everything was ok. However, they doubt the file is actually on the supplier FTP server, and don't believe the desired folders have been created, so they skip using FM and use their FTP client ("Fetch") instead. Compliance is a challenge... I would like to show them the FTP directory much like the they see it in Fetch (actually I believe I need to do better...) and I have everything ready, except for this part. When they are in Fetch and get disconnected, Fetch will not tell them and will keep showing the directory, and if they click a folder it will reconnect seamlessly and open the folder. Same thing if they drop a file on the window, it will reconnect and upload. The way they use Fetch, they might be "connected" for 15 minutes or so. I'm thinking that the easiest way to achieve a similar behaviour with FM/360 is to make sure the connection stays open. I was testing with FTPeek_GetCurrentDir (set to a variable, without using the result), and it looks like it might do the trick. Still, that is a workaround, so keep me informed if you fix the problem.
  3. I tried using this function to keep the connection active, but it seems it still gives me "1" even when the FTP server has disconnected. If I connect, then use this to check every 30s, then leave it for 10 minutes or so and then try uploading/downloading a file I get error as if I am no longer connected. Is it actually checking with the FTP server? If not using this function, any suggestions on how to keep the connection active (we are talking minutes, not hours)?
  4. Sorry for the incomplete info. Using Email 3.2 (latest) on OS X High Sierra (latest update) on the server (I'm talking about PSoS) and I'm reading emails.
  5. Yep, I found elsewhere that the problem with FTPS in connection with firewalls is that it starts with secure communication and then negotiate the port where communication will continue, meaning that the firewall won't be able to detect the port. Apparently this is why FTPS is seen as an outdated technology and SFTP is recommended.
  6. When running PSoS, I thought the attachments would be stored in the temporary folder and removed when the PSoS-session is over. I find that each attachment creates a folder like "UID@email.com" in the Documents folder, and it stays there after the session. I tried to make the script remove it, but ran into some problems. Any suggestions?
  7. Here's one more who wish for this feature. I would try the suggested one above, but I thought it was not working so we agreed another solution with the one supplier that used this. Anyone tested this and could confirm it works?
  8. I have a similar problem with ftps. It is actually working fine as long as I do it from the client, but when I do PSoS I get "java.net.SocketTimeoutException". I'm guessing it might be that ftps use another port which is not open in the server's firewall?
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.