July 11, 200718 yr When selecting a element(fk -from a value list) in a portal- the wrong/next element [in this case a new foreign key] is created then stored instead of the value list element I clicked on. [color:red]See attached file for demo There seems to be an increment error: I have 4 tables: shootme_a shootme_b shootme_c [the problem child table] shootme_ab [this is a join table between A and B] Viewing from shootme_a, i can select elements of shootme_b (using a valuelist in a portal located in Layout "Shootme_a"- seen via drop down. "[color:green]fk_b"- see attached file for demo) and add records in shootme_ab(the join table).. this works. But when i try to choose a value from the linking table (shootme_ab) in shootme_c via a portal, i am provided a list of jointable entries(ab_combined) yet upon selecting a value from [color:blue]ab_combined FMP swaps in a foreign key that doesn't exist!? Producing an error in data entry.(the fkey that FMPro adds is a new record number ie. last FK + 1. When i reselect it..it then stores the value properly but it (portal to table shootme_c) also creates and stores a bogus fk(fk+1) even though table shootme_c has no privilages to do so. What gives? and much more importantly how do i have the table shootme_c select and store valuelist items correctly, and not add bogus elements to the join table join_ab? What should happen is table shootme_c allows users to select elements from table shootme_ab, and store them in table shootme_c without creating any new records in table shootme_ab. Any help would be appreciated, -enki shootme.fp7.zip Edited July 11, 200718 yr by Guest
July 12, 200718 yr First off, pk_ab is data type number, while the fk_ab is data type text. Mis-match is not good. You should also put delimiters between the concatenated values: otherwise 1&111 = 11&11 = 111&1 = 1111, which would further add to the confusion. Secondly, table a, b and c is meangless to me. If you want meaningful help, give me a meaningful example like invoice lines, customers, etc.
Create an account or sign in to comment