Update of Free White Paper for FMP Novices

[David Kachel]

FOR IMMEDIATE RELEASE - NOV 14, 2005

WHITE PAPER FOR FMP NOVICES - VERSION 1.06 RELEASE

Salt Lake City, UT--NOVEMBER 14, 2005--David Kachel/Codemasters Workshop -- publishers of AutoNavigator for FileMaker Pro--Today announced the latest release, version 1.06 of their free WHITE PAPER FOR FMP NOVICES.

WHITE PAPER FOR FMP NOVICES is a compilation of important advice not available anywhere else. No newcomer to FileMaker Pro should be without it. Updated and expanded from 60 to 70 topics, this white paper covers important subjects concerning the proper design of a database solution in FileMaker Pro and mistakes to be avoided. Now 58 pages long, it is a must-have for any FileMaker newcomer and is free to download.

Don't put yourself in the position of having to do a complete rewrite of your database because of fundamental design flaws. Get this white paper and learn the secret ins and outs advanced developers have had to learn the hard way.

This document will be updated frequently as new entries become available. Check back often for new version numbers.

WHITE PAPER FOR FMP NOVICES is available for immediate download at: www.codemastersworkshop.com/downloads.html

Publisher:

David Kachel / Codemasters Workshop is the publisher of

AutoNavigator for FileMaker Pro. He has more than 14 years

experience in designing and building custom solutions in FileMaker Pro.

###

© Copyright David Kachel/Codemasters Workshop. FileMaker Pro is a

trademark of FileMaker Inc. All rights reserved.

David Kachel

Codemasters Workshop

email: [email protected]

web site: http://www.codemastersworkshop.com

ICQ: 308137637

Tel: (801) 566-1340, (801) 661-2454

[Siri]

I'm not sure if I should ask as question about the white paper here?

I'm a new user trying out techniques I'd like to use later.

In the section about editing portals on a 'platform' next to the portal list.

The way I understand this idea is that you transfer the record that you'd like to edit to the'platform' by copying the data into a 'global record' in another table. The fields on the 'platform' are actually fields from a seperate table and will then be copied back.

1. How do you make the portal non-editable or display only?

2. Is the global field supposed to be in a seperate table (or can it be).

3. In my case, the portal is into a join table for a many to many relationship. I'm not sure if this is preventing me from displaying the fields on the 'platform' correctly (I'm assuming the platform is just a graphic area on the layout)

Thanks, Siri

Inventorytest.zip

[David Kachel]

I'm not sure if I should ask as question about the white paper here?

I'm a new user trying out techniques I'd like to use later.

In the section about editing portals on a 'platform' next to the portal list.

The way I understand this idea is that you transfer the record that you'd like to edit to the'platform' by copying the data into a 'global record' in another table. The fields on the 'platform' are actually fields from a seperate table and will then be copied back.

1. How do you make the portal non-editable or display only?

2. Is the global field supposed to be in a seperate table (or can it be).

3. In my case, the portal is into a join table for a many to many relationship. I'm not sure if this is preventing me from displaying the fields on the 'platform' correctly (I'm assuming the platform is just a graphic area on the layout)

Thanks, Siri

No need to copy the record into global fields. Just add a new TO, make the relationship between a global field in the primary file and the key field in the secondary file. Create a script and put an invisible button (covering the entire portal row) in your portal that sets the global field to the key field for that portal row. Your record will appear in your editing fields.

To make the portal non-editable, just set all the fields in it to not allow entry.

A platform is just a visual separator that raises some fields off the background to indicate they are somehow different from the other fields on the layout.