Leaderboard

Hi, In command line, and using FileZilla, I can connect to SFTP by using username, server IP and a private key (.pem). In FTPeek v. 1.67, it seems that the public key is also required - I'm not sure about the password. How come? Is there a particular reason for this? Is there a proper procedure for connection using a private key file? Is there a list of the supported private key file types/formats? /David

Glad you got it to work. To clarify the issue from your first post today; Desktop isn't available to server-side scripting, as per the link posted earlier in the thread. Also, if you were to use my Path module, your code would automatically work on a Windows server as well. Right now, your code would fail if you did that.

your calculation value must be "un-stored" this way it will always evaluate to the current value. Choose storage options

I have the same need for public key authentication (without password). According to "how to use SFTP (with Client Validation - Public Key Authentication)" on: https://enterprisedt.com/products/edtftpjssl/doc/manual/html/howtousesftpintroduction.html "In public key authentication SSH clients and servers authenticate each other via public/private key pairs. Each must have access to their own private key, and they must have access to each other's public key. The client's public key must be registered with the SSH server, typically by copying it into the server's authorized_keys file. The client's private key is loaded via SSHFTPClient's setAuthentication method before calling connect, supplying the full path of the private key file, the SSH username and the passphrase of the private key file. and on this page: https://enterprisedt.com/products/edtftpjssl/doc/manual/html/howtousesftpwithclientvalidationpublickeyauthentication.html Public Key Authentication involves using a private/public key pair to authenticate the client. The key pair must be in a file in OpenSSH or SECSH format and the name is passed as follows: ftpClient.setAuthentication("myprivatekey", "jack", "my_keyfile_password"); The user-name is the name of the user on the SFTP server, but the passphrase is the password for the key-file (if there is a password). Using Transmit from Panic Software, I choose the "SFTP" protocol, input the "server address", enter my "User Name", then choose my private SSH key instead of a password, and then put in a remote relative directory path to get files and the local path to receive them. Now, according to an April 7, 2014 reply from Joe Pampalon of 360Works: "FTPeek does not currently support this SFTP connection method, but 360Works can custom develop the plugin to suit your needs. Please send an email to infobox@360works.com if you are interested to receive a quote for the work." This is a very common aspect of connecting to SFTP servers. Is this still a "develop to suit" feature, or is it possible to accomplish with FTPeek? If supported, how do we do it, and which versions of FTPeek support SFTP authentication via keys without a password? Thanks in advance, - - Scott

Thanks for the replies guys. I found a solution. In my script I do a Perform Find with two criteria. The first compares a variable I set in the parent table for the movie name with the movie name in the child record. That covers any child records with identical string values. The second does the same except I add " ("* So basically it just adds literal text and zero or more characters beyond that. The logic is clearly not watertight, but it fits the conditions I need it for. Thanks again for the help, I'm looking into the suggestions anyway as they are quite clever and may be of use somewhere else in my database. Best, Mark

That is true, I can't think of any situation where there would need to be more than one sending address (probably against some kind of standard as well). There may be something simple that can be changed. I suspect that the same email address validation code that checks the "to" parameter also runs for the "from" parameter and in that logic, it checks for a "," the presence of a comma tells the plugin that there is a list of email addresses, it then takes the text preceding the comma and checks for the presence of an @ symbol. I will create an issue in our issue tracking system to review this but for now you will need leave the comma out or enter the name as firstName LastName <emailaddress>.

Hey there, Basically, when using XML, MirrorSync relies on the script steps to perform operations. When using JDBC on a server to server sync, I believe our script steps aren't being utilized at all as all communications occur over JDBC. However, for a Server to Pro/Go configuration, we do rely on script steps to hit FMPro/Go solutions (while using JDBC between the Server and MirrorSync). If your sync is server to server, then you can ignore the inability to copy and paste these steps. Otherwise, we do have to respect that restriction. It's a limitation imposed by FileMaker as to how many steps you can have in one script. I'll see about modifying that prompt to provide a little more information on the nature of script steps' max capacity and MirrorSync. I've known of customers who also opt into breaking their configuration into 2 smaller configurations, though this can be complex. You'd have to make sure the tables in each configuration were not related to tables in the other configuration, as otherwise conflicts can occur. It's not a strategy we currently support, though I've seen it work. Hope this answers your question. If you want more clarification or want to pick our brain about something, please don't hesitate to email or call us at support@360works.com / 770.234.9293!

A script like this should work (test on copy of DB). Go to Next Field //To select any field Set Variable [$field; Value:Get(ActiveFieldName)] Freeze Window Enter Find Mode [ ] Loop Set Field ["="] //Don't specify a field Go to Next Field Exit Loop If [$field=Get(ActiveFieldName)]//Exit loop after you looped thru all fields and return to the first field. New Record/Request //Create an 'or' Find End Loop Perform Find [ ] It would help to make a layout from the same TO and only put in the fields you want to search. Then the first script step would be to go to that layout, and the last script step would be to return to the original layout. I still believe preventing the user from creating a record and not being allowed to leave any field blank that should contain data.

Or this one: Let ( url = Substitute ( GetAsText ( YourContainerField ) ; "." ; ¶ ) ; RightWords ( url ; 1 ) ) EDIT: For v13, use Let ( a = GetContainerAttribute ( yourContainerField ; "filename" ) ; RightWords ( Substitute ( a ; "." ; ¶ ) ; 1 ) )

Just to let anyone know that may have the same issue, I have submitted this to 360works support and they replied that this is a confirmed bug and recommend to go back to ver 1.67 until a fix has been issued. -Sydney