There are several commands in Sesame that save files. How are you obtaining or producing a .pdf file so that it needs to be saved from Sesame?

Generally, pdf files are produced by writing to a PDF printer driver. Most of these allow you to either send the result directly to a printer or save the result as a .pdf file.

If you are saving the file directly from the scanning software, there is no need to "save the file" from in Sesame. The file is already saved and exists in your file system. You will need Sesame to reference the path to the file.

If your scanner software is saving the file to c:\MyDocuments\scanned_234.pdf, you could have an element on your form for the PDF file that contains the string representing the path "c:\MyDocuments\scanned_234.pdf". If you named the file uniquely, setting this element to the path could be automated using mass update or on application / form open programming. Once the element has the path, you can use PDF viewing software to display the PDF from Sesame.

If having the PDF file exist outside the Sesame application is cumbersome, you can use a "base 64" converter to convert the PDF file into ASCII, and then @insert the file into an element, thereby storing all of the PDF content actually in the record. It would need to be restored as a PDF before it could viewed, each time it is viewed. Your application file will grow quite large (base 64 is 1/3 larger than the original binary) and there will certainly be a performance hit, but it will result in a central container. In this case, you would need to "save the file" from Sesame in SBasic, to have a base 64 file to convert back into a PDF to display with a pdf viewer. SBasic has a full complement of file commands, including FileOpen, FileClose, and FileWrite.

So you are not trying to save a file, so much as you are trying to copy a file from one path to another?

You can either let the OS take care of it using @shell or any of its variations, or you can use the FileOpen command to read the file and write the file to a new location (path and name). @Shell is probably the simpler solution, but may not be quite as elegant, in that a command line window will appear briefly. FileOpen is a bit cleaner, but does involve a bit more SBasic programming.