Portal help - cant edit / add rows

[Inetmaster]

First - Sorry for the cross post - I realized I posted this in the wrong forum.

I'm a newbie to FM development and am hung up on what to do here.

I have a few tables (please see attached PDF for my relationships graph) that are related that I want to reference in a portal.

I want to associate Items to an Auction. The auctions table is related to an AuctionItems table. Items are related via the AuctionItems table. On a layout, I have details of an auction, and want to be able to add predefined items (from the items table) via a portal. I would like the fields Item Number and Item Desc to show in the portal.

I **should** have my portal and relationships setup okay, but I am not for sure.

I'm having a few issues:

1. If the fields in the portal are left as Edit Boxes, I can click in them, but not type any data in - it seems it is not accepting keyboard input.

2. I would prefer to use a Value List of all the Items in the Items Table to make data entry easier. I can successfully setup one of the fields to be a Value list popup or menu, but choosing an items does not populate the fields.

3. I'm a newbie, so I am no script expert. I thought of opening a new window to allow the user to see a list of all the items. If I use the command, Set Field[AuctionItems::Auction; Auctions::uid), an entry is created in the AuctionsItems table, which will show an extra blank entry in my portal. What I could not figure out in this approach is how to populate the same row filling in the AuctionItems::Item field with Items::uid - a Set Field in the same script with a button 'Resume Script' did not seem to work between windows, but this may be by Filemaker design, and I just didn't know that.

Thanks for the help - I'm really stuck on this one....

Wayne P.

PaymentPortal.pdf

[teckert]

for the first part of your question hs your relationship been setup such that you allow records to be created in the related field based on the relationship, check this through the relationship tab of define database

[Matthew F]

I suggest that you don't use the Field Name "UID" for each of your tables since the UID of the Auction is not the same as the UID of the Items. I would rather use "Auction UID" and "Item UID", for example.

Regarding Question 3: If you are running a script on a layout with the Auctions table you don't need to set the AuctionItems::Auction field. This is the Match Field between the Auctions table and the AuctionItems table and so data will be entered automatically in this field when you start to enter data in any of the other field in this portal. You should leave this field off of the portal altogether.

Are you sure that you need all three tables Auction, AuctionItems, and Items? It would seem to me that the Auction Items table might be superfluous, and its fields could be incorporated into the Auctions table. You don't need to put all of the auctions fields on any given layout, for example. As it stands you have created a many-to-many relationship between Auctions and Items, which means that, not only can an auction have many items, but an item can also have multiple auctions.