Sorry if this has already been asked, but I wasn't able to find an answer.

I'm trying to set up a link from within my Filemaker database that would open a specified folder (in this case, the file path would be based on a calculation). I'm currently using Container fields to display images stored in a folder. Essentially, all I'm trying to do is include a link on that screen that would open that folder up.

The caveat, potentially, is that the container fields aren't permanent. They're just global fields that pull in the appropriate image when someone wants to view it. Since all the actual image files are saved on a server, the need was only to be able to view through the database frontend, not store.

Thanks in advance for any help.

Can't be done without a plugin. That is, you cannot point FM to a specific OS folder.

PS: I'll move this to the appropriate sub-form. Check out 360works Scriptmaster (it's free).

Can't be done without a plugin. That is, you cannot point FM to a specific OS folder.

Well, you know what's going to happen when you put it like this...

OpenEnclosingFolder.zip

Not tested on Windows.

BTW, you could also use Perform AppleScript[] if on a Mac and - I believe - Send Event[] if on Windows.

Alright, I'll look at this fancy script. Give me a couple of days, though.

I'll have to check that out.

I should have probably also mentioned that I'm trying to set this up for users in a mixed environment, so any solution would ideally be compatible on both Macs and PCs.

Michael,

It works perfectly on Windows as well!

Thanks - I couldn't remember if Windows required another slash or not.

Brilliant.

I read too quickly and didn't realize that he'd have the path to the file (and therefore would be able to calc the directory).

I'm sorry, I just realized I never checked back in on this. Your solution took a little bit of tweaking to make it fit, but it worked really well. Thank you!

I just saw that script and it has a Go To Field(nothing). Can you explain why you put that? I watch and it makes me leave the field but so does commit records. and the action looks identical when I run it so it must be something behind the scenes.

There is practically no difference, esp. if the layout is set to commit automatically. However, I prefer to use Go to Field[] when the purpose is to deselect - even if the record may be committed as a result.

Hello Comment, thank you for taking time to respond. First time in reading a zillion of your posts that something doesn't fit.

even if the record may be committed as a result.

So you are using it, not to commit the record, but to leave the field (deselect). As far as I can tell, that action always commits and the person may not be ready. Is it not in this 'tween' state where person is possibly entering data in new record and has option to revert (even removing children if any were created at same time)? There must be other protections you use then in most cases or there is something about this specific demo that creates an exception. You do not always use that do you?

I picked up idea of using Go To Object[Object] from LaRetta a few months ago which leaves the field but does not commit. I realize I must make many decisions about committing when working with scripting under covers. But when on layout with person then I think the person should decide whether and when to commit their entry. Am I wrong?

No, you are not (entirely) wrong. However, this demo is not about committing or reverting - and as a rule I try to keep them as simple and as focused as possible. Perhaps I should have simply left the cursor in the container field.

As far as I can tell, that action always commits

I am not sure I'd agree with the "always" part.

First time in reading a zillion of your posts that something doesn't fit.

I am sure there will be others... :laugh2: