Jump to content
Claris Engage 2025 - March 25-26 Austin Texas ×

This topic is 5168 days old. Please don't post here. Open a new topic instead.

Recommended Posts

Posted

Dear All,

I am working on file in which for "export field contents"Script step i have given hardcoded path in Path which is stored in variable.

Problem is come when i export the field contents and its save data in Filemaker folder where filemaker is installed .

Is there anyway to find out location of your export field content data .means where your export content is save?

For example i use 1 variable name $Path and give my hardcoded path into that variable and in "Export field content" Script step i have given that $Path variable in Path of Export filed content script step..Now is there anyway of finding out where that Export field content is save .----Is it your given Path or in Filemaker folder?

Posted

Problem is come when i export the field contents and its save data in Filemaker folder where filemaker is installed.

Not a good idea saving to the FileMaker folder.

Only save files to the temporary folder or the documents folder, and maybe the desktop folder. These are the only folders that the user will have privileges to write to. Any other folder including the FileMaker application folder will probably be read-only, especially in a corporate environment where the user does not have admin privileges to the computer.

FMP has functions that return the path for desktop, documents and temporary folder.

Posted

You are not getting my point.when we give path in export filed content and if that given path is not valid then by default Export field content data saves in filemaker application folder.you can try this by giving wrong path in variable with save_filename and put this variable into Export field content then it will automatically save your content in Filemaker Folder.

Like in $path set Filemac://Users/Public/Me/abc.txt path in it.

when you will give this $path in Export field content then it will save in Filemaker Folder.

My problem is starts from here it saves data into Filemaker folder and i thought it saved in my given path location...it dont give error message.

Posted

You are not getting my point.when we give path in export filed content and if that given path is not valid then by default Export field content data saves in filemaker application folder.you can try this by giving wrong path in variable with save_filename and put this variable into Export field content then it will automatically save your content in Filemaker Folder.

Like in $path set Filemac://Users/Public/Me/abc.txt path in it.

when you will give this $path in Export field content then it will save in Filemaker Folder.

My problem is starts from here it saves data into Filemaker folder and i thought it saved in my given path location...it dont give error message.

Genelia..

Posted

if that given path is not valid then by default Export field content data saves in filemaker application folder.

That's not my experience at all. If the path is not valid, you should get an error message "abc.txt could not be created on this disk. …".

Moreover, the path you mention:

Filemac://Users/Public/Me/abc.txt




is not a valid Filemaker path. An absolute path should look like this:




"filemac:/YourVolumeName/Users/Public/Me/abc.txt"

Check carefully what is stored in your export script step, besides the $path.

Posted

Ok thanks.

but it is very strange for me when i again checked the path then it took "filemac:/ Macintosh HD/Users/admin/....."

when i put these 2 spaces before Macintosh HD it started to work correctly.Anyway i have sorted out the problem.but why there are 2 spaces before the Macintosh HD Path? i dont know the answer.

Thanks,

This topic is 5168 days old. Please don't post here. Open a new topic instead.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

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