More often than not, it's a rights issue - the user doesn't have rights to the path the file in which the file is trying to be created. If you can modify the rights of the target directory, you should be fine.
The temp folder likely isn't there. Restarm FM and it should work. If the issue persists, you need to find out what is nuking the temp folder.
1 of 1 people found this helpful
At first blush, I don't particularly like the "FullyQualifiedFieldName" part, not the path or the permissions.
If you mean what you say, and the exported file name contains the double colon (::) that FileMaker puts into field names, then that would almost certainly cause a problem on Macs using the standard partition scheme, which is really using a colon under the hood, and not the forward slash we can all see & type.
What's wrong with setting up a name that looks like:
Let ( [
now= Get ( CurrentHostTimeStamp )
; year= Year ( now )
; month= Right ( "00" & Month ( now ) ; 2 )
; day= Right ( "00" & day ( now ) ; 2 )
; hour= Right ( "00" & hour ( now ) ; 2 )
; minute= Right ( "00" & minute ( now ) ; 2 )
; seconds= Right ( "00" & seconds ( now ) ; 2 )
; filename= Get ( FileName )
; tableName= Get ( layoutTableName)
; result= year & month & day & "_" & hour & minute & seconds & "_" & fileName & "_" & tableName & ".fpsl"
) // end Let
You can also throw in the user's name as well, if you like. Using the field name seems unnecessary to me anyway. What is the field name you are using?
-- Drew Tenenholz
Drew, Thank you for your response. I guess I should have indicated that the calc doesn't literally say "FullyQualifiedFieldName"; I just meant that a field name, preceded by "TO"::, goes there, not that actual text. In one script, for example, the field is the name of the offer. As it happens, though, the name of this particular offer does not contain a couple sets of colons. I will look into that.
I'm sorry, I meant DOES contain colons.
Drew - It was the colons in the Offer name. Thanks for your input!