[FX.php List] Edit FileMaker portal information - FX.php FindAll information

Chris Hansen chris at iViking.org
Wed Aug 17 10:30:39 MDT 2005


There's a specific way to edit records in a portal.  This is also a way 
that multiple records could be edited with a single query.  Basically, 
here's how your line of code would look (assuming you've created an 
instance of FX called $myQuery):


where xxxx is the RecordID of the desired record INSIDE the portal (for 
FileMaker 7) or the portal row, numbered 1 through n (in FileMaker 
5/6).  Of course, right now the RecordID of portal records is not 
returned by default, but a simple calc field can be created that 
contains this information, and that field can be added to the portal on 
your web layout.

Hope that makes sense.

Also, a SINGLE new portal record can be created (assuming this is 
allowed over the relationship you're working with by appending a 0 
after the '.' instead of a positive integer.


--Chris Hansen
   creator of FX.php
   "The best way from FileMaker to the Web."

On Aug 16, 2005, at 6:25 AM, James Lawson wrote:

> Hi Group
> In FileMaker I store a Contacts telephone numbers, email addresses
> etc...etc..  in Portals throughout our databases.
> This information can easily be displayed with a FindAll with FX.php, 
> but I'm
> also wanting users to able to edit these when logged in over the web, 
> but I
> don't know the best way to do it - I see several options:
> --a)	write each FileMaker Portal row (i.e. FX.php related Table Record
> and Field) to a separate PHP Field in a Form, then upload the changed 
> fields
> one at a time via FX.php
> ==(thoughts: will mean increasing the edit hits on the database by a 
> factor
> of 30 times or more, however each FX.php edit update will be quite 
> simple
> for the server)
> --b)	writing each portal record to a single Flat Table in FileMaker 
> which
> has a field for each Portal row then get FileMaker to keep the two
> synchronised and FX.php will only need to call and edit the one Flat 
> Table
> ==(thoughts: high maintenance, will essentially have two data stores
> constantly synchronising)
> --c)	restructure FileMaker database to Flat Tables instead of using
> Portals
> ==(thoughts: not really an option - Portal technique fundamental part 
> of
> system)
> --d)	click to a separate webpage to edit each record that was a Portal
> row in FileMaker
> ==(thoughts: impractical users will not use the website)
> --e) ...open to any suggestions
> Any comments more than appreciated - thanks
> James
> _______________________________________________
> FX.php_List mailing list
> FX.php_List at mail.iviking.org
> http://www.iviking.org/mailman/listinfo/fx.php_list

More information about the FX.php_List mailing list