Search Project Mgmt
Search FileMaker Blogs

Thank you for visiting the FileMaker Thoughts blog. I recently moved this content over from my blogger account. Hope you like it! When you get a chance, check out the centralized search feature for all the FileMaker blogs found along the right side panel. It is quite handy!


Wednesday
May062015

The FileMaker FieldIDs Function

From Dwayne Wright PMP, PMI-PBA, PMI-ACP, CSM
Certified FileMaker Developer

WEB: www.dwaynewright.com
EMAIL: info@dwaynewright.com
TWITTER: dwaynewright
YOUTUBE: FileMakerThoughts

FieldIDs
FieldIDs( fileName ; layoutName)
All Current Versions Of FileMaker
Returns A Text Result

This design function will give you the internal FileMaker id number for all the fields on the specified layout. This will even work for related fields on the reference layout. Each internal FileMaker ID will be presented with a carriage return between each value.

As with most of the design functions, if you hard code the parameters of fileName or layout name, the results can be broken if you change the name of the file or layout afterwards.

=
More info about the author and FileMaker in general, contact me at info@dwaynewright.com.

© 2010 - Dwayne Wright - dwaynewright.com
The material on this document is offered AS IS. FileMaker Pro is the registered trademark of FileMaker Inc.

Wednesday
Apr292015

FileMaker Table Occurrences And Pick Lists

From Dwayne Wright PMP, PMI-PBA, PMI-ACP, CSM
Certified FileMaker Developer

WEB: www.dwaynewright.com
EMAIL: info@dwaynewright.com
TWITTER: dwaynewright
YOUTUBE: FileMakerThoughts

Many times in your FileMaker development, you have to pick a table occurrence for your reference point (generally referred as Context). In free form relationship design, every table occurrence is linked in one way or another. Think of it as a “Six Degrees Of Kevin Bacon” for the FileMaker developer. Anchor / Buoy does away with that by creating islands of linked table occurrences.

Here you can see where you set the relationship context for a layout.

Here you can see where you set the relationship context for a calculation.

After you choose the context, the number of items you can pick are shown. You will see table occurrences that have a relationship (based upon the context) to the current layout / calculation and what table occurrences do not have a relationship.

If you use a Spaghetti relationship design approach, you will likely see all possible table occurrences in the pick list because almost everything links to everything. If you use an Anchor/Buoy relationship design approach, this list is filtered because no two base tables touch (again because table occurrences are organized into groups or islands). So you can quickly and effectively choose just the related table occurrences you need and not choose a problematic table occurrence.

Here you can see a listing of related and unrelated table occurrences.
=
More info about the author and FileMaker in general, contact me at info@dwaynewright.com.

© 2008 - Dwayne Wright - dwaynewright.com

The material on this document is offered AS IS. There is NO REPRESENTATION OR WARRANTY, expressed or implied, nor does any other contributor to this document. WARRANTIES OF MERCHANT ABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE EXPRESSLY DISCLAIMED. Consequential and incidental damages are expressly excluded. FileMaker Pro is the registered trademark of FileMaker Inc.

Wednesday
Apr292015

Introducing Field Storage Options For FileMaker

From Dwayne Wright PMP, PMI-PBA, PMI-ACP, CSM
Certified FileMaker Developer

WEB: www.dwaynewright.com
EMAIL: info@dwaynewright.com
TWITTER: dwaynewright
YOUTUBE: FileMakerThoughts

As mentioned before, the dialog box for setting field options is set into the three tabs of Auto Enter, Validation and Storage. The third tab of the field options settings is for the storage of the field itself. FileMaker 7 has really opened up the options of field storage. This area allows for global storage, repeating fields and indexing. I will cover this in detail in following discussions.

QUICK REVIEW ABOUT GLOBAL FIELDS - The global field option is used to contain a single literal value for all records in a FileMaker file. Any field that has data stored globally has one value and it can be view no matter where you are in a FileMaker 7 file. By anywhere, I do mean that any global field in any table can be view from any record of any other table. Fields with the global option can be edited directly on a layout or via a script. Global fields work about the same as normal entry fields in that you can click inside them, cut, paste and add new data.

QUICK REVIEW ABOUT REPEATING FIELDS - A repeating field is any type of field ( except summary ) with a specific storage option setting. The storage option of repeating fields allows you to have multiple cells of information in the same field. As far as I know, FileMaker is the only database application that has anything like repeating fields.

QUICK REVIEW ABOUT INDEXING - FileMaker indexes focus on the data within a field. So if you have a FileMaker field indexed, FileMaker can look at it and go to the associated records quicker than it can if it is not indexed. For this reason, indexing is a key player in searches, sorts, reports and relationships.

Once again, I will cover these three storage options in detail in following discussions.
=
More info about the author and FileMaker in general, contact me at info@dwaynewright.com.

© 2007 - Dwayne Wright - dwaynewright.com

The material on this document is offered AS IS. There is NO REPRESENTATION OR WARRANTY, expressed or implied, nor does any other contributor to this document. WARRANTIES OF MERCHANT ABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE EXPRESSLY DISCLAIMED. Consequential and incidental damages are expressly excluded. FileMaker Pro is the registered trademark of FileMaker Inc.

Tuesday
Apr282015

FileMaker Relationship Caching And Refresh Window

From Dwayne Wright PMP, PMI-PBA, PMI-ACP, CSM
Certified FileMaker Developer

WEB: www.dwaynewright.com
EMAIL: info@dwaynewright.com
TWITTER: dwaynewright
YOUTUBE: FileMakerThoughts

In regards to the world of computing, the term of caching is a familiar term. In very broad terms, caching refers to a process of storing copied data in a place where it can be accessed quickly by a computer / program. This copying is done before the data is needed, in anticipation that it is going to be needed in the near future. So when the data is needed, it is gathered from the faster cache resource instead of the true place the data resides.

So let us say that FileMaker (the application) may anticipate a need from a user for record data. It may load that anticipated data into a local cache on the users computers, just in case. If the user does need the data, it is quickly available right there. Where do you think you might run across an occasion for something like this on a local level?

If you thinking of related data, we are on the same page. In a complex FileMaker solution, you might have dozens of relationships based upon the table occurrence you have associated with a layout. Those relationships likely have other relationships, that also have dependent calculations and so forth.

In some cases, FileMaker Join Caching may be working behind the scenes to give you fast and reliable data. It is possible that you might see a relationship that doesn’t seem to be accurate and you want to refresh it. In most cases, this freshen up is an update of the temporary storage cache with data from the actual resource. This is often called flushing the cache or FileMaker can call it “refreshing the join results”. You many find this command option is a number of places, most notably under the Records menu as a Refresh Window command or as an option in the Refresh Window script step.

Here you can see the Refresh Window script step with its options of cache flushing.
=
More info about the author and FileMaker in general, contact me at info@dwaynewright.com.

© 2008 - Dwayne Wright - dwaynewright.com

The material on this document is offered AS IS. There is NO REPRESENTATION OR WARRANTY, expressed or implied, nor does any other contributor to this document. WARRANTIES OF MERCHANT ABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE EXPRESSLY DISCLAIMED. Consequential and incidental damages are expressly excluded. FileMaker Pro is the registered trademark of FileMaker Inc.

Tuesday
Apr282015

The FileMaker Get(WindowName) Function

From Dwayne Wright PMP, PMI-PBA, PMI-ACP, CSM
Certified FileMaker Developer

WEB: www.dwaynewright.com
EMAIL: info@dwaynewright.com
TWITTER: dwaynewright
YOUTUBE: FileMakerThoughts

Get(WindowName)
Introduced With FileMaker 7
Returns A Text Result

The Get(WindowName) function is used to return the name of an active FileMaker window. Normally, this would be the active window in the foreground ( like if you have a field using this function on the layout ). However it is possible to use this function in a script that might be working on another window ( when used in conjunction with the Freeze Window script step).

© 2010 - Dwayne Wright - dwaynewright.com
The material on this document is offered AS IS. FileMaker Pro is the registered trademark of FileMaker Inc.