INSERT FILE script problems - How to get them out

[BruceJ]

Script step: INSERT FILE into a container field... I get how to do this, but then how the hell do I get the file out?

I understand that I can "export" the file, and then have to change the suffix to the proper file type (e.g. ***.pdf or ***.doc and so forth). But my users can't even figure out the differences between right click and left click let alone know how to go adding suffixes to file names.

I know FileMaker hadn't intended for this to work this way but I cant find hide nor hair of it in the Help files, so what't the proper and easy way to open files stored in container fields?

(PS - I know that if I drag and drop i can open them, it's the script step that doesn't work for me. I know the reason has do do with binary encoding, yada yada yada... but I need the "how to" and not the "how come".

Version: v7.x

Platform: Windows XP

[loogi]

Hi Bruce

I am glad i am not the only one who finds this disturbing. This function is not any problem if all users are professionals, but normally they are not.

I would also be really glad to know about a solution to this problem.

[BruceJ]

bump to top...

Any advice or insight would be helpful! Thanks.

[Ocean West]

You cannot open files that are STORED in a container you can only export them via the menu, contextual menu. or via a script. Once they are exported to your destination you may open and modify your data.

[BruceJ]

Thanks, my problem is in the exporting, it leaves off the suffix and the uses has to physically change the document suffix to open it with the appropriate application (e.g. "*.doc, *.jpg, etc)

Perhaps this is a Windoze issue. regardless, my users aren't sophisticated enough to know what suffixes to add to the file name after it's exported. Is there a way around this?

[Steven H. Blackwell]

Use the new export field contents feature--not export the data.

Steven

[pspafford]

Hey Bruce,

With the SendEvent script step, you can send DOS commands.

Create a plain-text file called toDo.txt. Move it to the same directory as your solution. Then use this SendEvent:

cmd /c ren toDo.txt toDo.DOC

The "cmd /c" starts the command line interpreter. "ren" is the command to rename. "toDo.txt" is the original filename and "toDo.DOC" is what you want to rename it to.

If you will be doing this in a directory other than the one your solution is in, you will have to specify paths for the filenames, using quotes. Something like:

cmd /c ren "c:windowsdesktoptoDo.txt" "c:windowsdesktoptoDo.DOC"

... and of course, you can use calculations to build this. Do a search in the help file for "operators" to see how to treat backslashes.

Paul

[sourfunk]

I may be the complete novice to whom you are referring. I read about File Maker Pro 7 and thought it would let me organize a document portfolio like I've been wanting to for several years.

What I expected to be able to do was make a record that had several text fields with various bits of information and one container field that would actually store a pdf. I wanted to be able to easily open the pdf if the information stored in my fields didn't give me everything I needed in a particular case. I thought I set this up, but I can't figure out a way to open the pdf. If I only "store a reference to the file," I can open it, but I want the actual file saved in the database so that when I back it up I know that I've got everything I need.

It seems like given all the other difficult stuff Filemaker can do, it would be able to open my PDF for me.

Can I set it up to open the pdf?

[bruceR]

If you store the PDF as a movie, you can view the entire PDF in place.

[bruceR]

Old Advance Man said:

Use the new export field contents feature--not export the data.

That is a great feature. But I am quite suprised to see that you can't control the export process by using data, where you would use a field to control the export path and exported file name. You need to use plugins/applescript/send message commands; unless I'm missing something.

[John K]

Well,

you and I are thining the same. I've been wanting a document library for a while now. Now, i'm on a Mac, so i don't know if this is helpful, but what I did was incorporate some Applescripts that, which I import a file, grabs some basic information about the file (i.e. extension, original path, size, last date modified). It writes this data to a set of fields. Then, when i go to export a file, I can export it to it's original location (creating that location if I need to) and, based on the file extension, adding that extension when I export it. Finally, when I import the file, based on the file extension, I've hard coded some if then statements that, based on the extension I insert the file in a particular way (i.e. images so I can view them in the DB or files for storage.)

Version: v7.x

Platform: Mac OS X Panther