sal88

Are you aware that the temp paths are different on the server? https://fmhelp.filemaker.com/help/16/fmp/en/index.html#page/FMP_Help/paths-in-server-side-scripts.html

Try "BE_Curl_Set_Option ( "BE_CURLOPT_FORCE_STARTTLS" ; True )" before the BE_SMTP_Server step, or remove username and password. Also double check you can send via your smtp server with other means, i.e. Outlook. Or, if the attachment was created by filemaker in the first place, try and manually insert an attachment in to the attachment field and try that.

Have you tried doing away with the export step and just emailing straight from the container fields? BE_SMTP_AddAttachment will allow you to add the container fields instead of file paths.

Thanks I'll take a look! it was on the back burner, but now it looks like we may be embarking on the journey again. Needs a bit of a rethink as to what they're actually after. I'll let you know. Cheers!

Does anyone have any ideas on this? I've added another picture to give a better idea of how this looks.

Have you tried the text file registration method?

Hi all I've switched from the 360works scriptmaster plugin to baseelements for sending emails. Since then, subject lines that contain spaces have tabs in as well. The tabs are not necessarily in place of the spaces, as subjects with many spaces have just the one tab. In subjects with just one space however, the tab replaces that space. I hope the picture shows what I'm experiencing. The header of the email contains the following: Subject: spaceatfortiethcharacterspaceatfortieth characterspaceatfortiethcharacterspaceatfortiethcharacterspaceatfortiethcharacter So it appears as though it may be adding a carriage return? Any ideas? I've just double checked that it is OK with 360works and it is indeed! The only difference I can think of in the way the plugin talks to our exchange server is that BE requires there be no credentials but 360 requires credentials.

Thanks Fitch! Very happy to hear that!

Hi all I have three backup schedules: hourly, daily and weekly. To reduce any lag experienced by end users during the day I am wondering if I should do away with the verification step for the hourly one, which would speed up the backup. I would keep it on the other two and would be emailed by FMS if there were an issue. But if there were a crash and I wanted to restore from the hourly one, how do I know the data integrity is OK? Obviously if there were an issue I would use the older daily one, but that is a risk I'd be willing to take if it sped things up. Thanks

Hi bcooney I don't suppose you could clarify what the difference is between ESS and what I am doing here? This looks promising in terms of doing INSERT from SELECT: https://www.soliantconsulting.com/blog/executesql-filemaker However I have a few hurdles before I get to that point. Here is what I have done so far: I have my ODBC source set on the server which hosts our filemaker solution. On my local machine I have to locally add the ODBC source in order to use the "Execute SQL" script step. It does not see the ODBC source that I have set up on the server. I also cannot add the local ODBC source to 'external data sources'. Now I can create a new record in the external SQL source using "Execute SQL" (and the locally added ODBC source) however it takes a very long time for the new record to appear. I am viewing the record from a layout that is based on the server's ODBC connection (not my local ODBC connection). The new record definitely gets created however as if I try to perform the same operation with the same ID it complains that the ID is already in use. Also if I connect to the ODBC source from MS Access then I see the record straight away. The idea is that a script will run on the server every hour that will delete the records in the external SQL table and then populate it with records from the FileMaker database. Will this be possible given that I can only select my locally added ODBC source in the "Execute SQL" script step. If someone could point me in the right direction that would be great! Many thanks

Brilliant! that works. thank you very much Olger!

I'm still stuck on this - I can't work out if ESS is even meant for my purposes. Any help whatsoever would be much appreciated. Many thanks

Hi all I'm trying to export my filemaker records to my external sql database via the execute sql script step but am getting a number of errors. I can see my external ODBC source and can generally write to it (I can go to the respective layout and click 'new record'). My query basically as follows: "INSERT INTO dbo.Log ( dbo.Log.log_id, dbo.Log.log_case_idf, dbo.Log.Labour_TOTALS_Labour_Cost, dbo.Log.Labour_TOTALS_Item_Sale) SELECT Log_Log.log_id, Log_Log.log_case_idf, Log_Log.Labour_TOTALS_Labour_Cost, Log_Log.Labour_TOTALS_Item_Sale, FROM Log WHERE Log_Log.Log_Type = '2'" My first question is: is it even possible to export to an odbc source with a 'insert INTO SELECT' query? Many thanks

No i just ticked the Enable ODBC/JDBC checkbox on the server. I tried to add the DSN from my client machine. The DSN is on my local machine.....Aaaaand I've just set up the DSN on the server instead and I can now see it! I take it this is the correct and only way for it to work for a hosted database?

I can see the DSNs in a newly created local blank database. However when i upload this to our server the DSNs no longer appear. I've enabled ODBC in filemaker server but no joy.