Log in to create and rate content, and to follow, bookmark, and share content with other members. Not a member? Join Now!

AnsweredAssumed Answered

Loose Links to External gif Container Field in Runtime

Question asked by hsutton47 on May 26, 2012
Latest reply on May 28, 2012 by hsutton47

Like • Show 0 Likes0
Comment • 2

Title

Post

I have a video database with a container field for the thumbnail of the movie. To keep the db from getting very large I do a reference to the gif file located in a folder called "movie_thumbnails" vs. storing the gif in the field itself.

Once I get this working well, I plan to create runtimes to give to a couple people along with the folder of movie_thumbnails. Problem is, when I create the runtime and simulate putting it on another computer, even though I am using the same folder hierarchy with the same folder names and relative paths, the thumbnails do not appear. Just a text stating the referenced file is not found.

Is the only way to make this work is to store each gif inside the filemaker db prior to creating the runtime solution?

No one else has this question

Outcomes

2 Replies

davidanders May 26, 2012 4:25 PM

Relative

The path to a target file specified from the current database’s location. If the current database is opened remotely, the path starts from the local FileMaker Pro directory

file:directoryName/fileName

filemac:directoryName/

filewin:../fileName

=During the development of a database with multiple files, you may want to have some of the files in separate folders. During the creation of a runtime database solution, however, all files are moved into the same folder as the runtime application.

For this reason, include a path that is just the filename of the file being referenced. Although the runtime application will check other data sources, it will then be able to find the file in the same folder in which it resides. You can still keep any absolute or relative paths in the same data source in case the files are also used in FileMaker Pro or FileMaker Pro Advanced.

Home > Using FileMaker Pro Advanced > Using FileMaker Pro Advanced tools > About creating runtime solutions (FileMaker Pro Advanced) > Preparing files for a runtime solution (FileMaker Pro Advanced)

Preparing files for a runtime solution (FileMaker Pro Advanced)

Before you bind files into a runtime application, decide if you want to:

•

Let users open and close auxiliary files: In the runtime application, there are no menu options to open or close files. If you want users to open and close auxiliary files, you must provide scripts in your solution to perform these operations. In each auxiliary file you must place a button or startup script that returns users to the primary file.

•

Let users modify the database: Unless your runtime database solution files are password-protected, users can open and modify the files in FileMaker Pro or FileMaker Pro Advanced. You can also make your files permanently unmodifiable. See Removing Admin access to databases (FileMaker Pro Advanced).

•

Create a cross-platform runtime database solution:

If your solution will be used in Windows, bind it using the Developer Utilities for Windows.

If your solution will be used on Mac OS X, bind it using the Developer Utilities for Mac OS X.

See Binding files into a runtime solution (FileMaker Pro Advanced).

If you’re creating a solution to be used on both Windows and the Mac OS, create two separate runtime solutions by binding the original solution files twice: first using FileMaker Developer Utilities for Windows, and then using FileMaker Developer Utilities for Mac. Use the same binding key on both platforms.

•

Provide updates for your users: You can make it easier for users to update your runtime database solution files by providing scripts in your primary file to export their data and import it into the updated solution.

See Importing data into upgraded runtime solutions (FileMaker Pro Advanced).

•

Let users print reports or other information from your runtime database solution:

It’s a good idea to set document margins if your runtime database solution will be printed from a variety of printers.

For more information, see Specifying page margins.

•

Let users perform spell checking on records: You can change the main spelling dictionary language for your database solution by choosing one from the dictionaries supplied with FileMaker Pro Advanced. Your users can add or modify a user-defined dictionary to the runtime application.

For more information, see Creating and selecting spelling dictionaries.

Verifying FileMaker data sources

In addition, if you have been preparing multiple files in separate folders, you need to verify FileMaker data source references. A data source stores the file path or paths that the runtime application searches to access an external table, script, or value list.

=During the development of a database with multiple files, you may want to have some of the files in separate folders. During the creation of a runtime database solution, however, all files are moved into the same folder as the runtime application.

For this reason, include a path that is just the filename of the file being referenced. Although the runtime application will check other data sources, it will then be able to find the file in the same folder in which it resides. You can still keep any absolute or relative paths in the same data source in case the files are also used in FileMaker Pro or FileMaker Pro Advanced.

=The Manage External Data Sources dialog box lists the data sources in the current database. Be sure that for each FileMaker data source, there is a reference in the File Path that is to the filename only, without any folders. The data source will look like this: file:MyFile.fp7. See Connecting to data sources for more information.

=Tip You may want to put multiple tables in one file to avoid problems with FileMaker data source references.

Note =FileMaker Pro Advanced may not be available in all of the shipping languages of FileMaker Pro.

Related topics=

About creating runtime solutions (FileMaker Pro Advanced)

Naming runtime solutions (FileMaker Pro Advanced)

Distributing runtime solutions (FileMaker Pro Advanced)

Starting runtime solutions (FileMaker Pro Advanced)

Recovering runtime files (FileMaker Pro Advanced)

Actions

hsutton47 May 28, 2012 5:32 AM
Mark Correct
Correct Answer
Thank you. I had researched for a while and actually read the help info you pasted into your reply before posting my question. I thought I was doing what that information stated to do, retaining the relative path to the grahics gif folder with the runtime folder group, however, the graphics were in a parallel folder to the runtime project folder. When I re-read the information you provided, the key words that stuck out this time that I did not pick up on the first time was that all external support files must be contained within the runtime's project folder. So I dragged the gif folder into the runtime folder and all is now working fine. I do not know how it reconciles itself compared to how the folders are laid out in the actually filemaker folder structure, but it does. Thanks.
Like • Show 0 Likes0
Actions

Loose Links to External gif Container Field in Runtime

Title

Post

Outcomes

=During the development of a database with multiple files, you may want to have some of the files in separate folders. During the creation of a runtime database solution, however, all files are moved into the same folder as the runtime application.

Related Content

Recommended Content