2. PHPRunner General questions
  3. Question about architecture / data inheritance
This topic is locked

Question about architecture / data inheritance

 		4/24/2020 4:39:15 PM
PHPRunner General questions
N
 nagate816 authorDevClub member

Hello,
I have been using PHPRunner for about a year now but for relatively simple projects and I have a requirement that is a little more complex so I'd like to ask your opinions on the best way to set it up.
The application will hold Requests. The Request form in itself will have about 40 fields that get entered manually but will have two sections (one for the Requester and one for the specific program) where the data will be held in separate tables and each will have 10-15 fields of data. These fields in the Requester and Program tables will need to be "pulled in" as part of the Request but I don't want to use the Parent - child form as the data (like the Requesters name, address, etc needs to be in the same form not in an expandable view like with the parent child. HAs anyone done anything similar to this and have any advice ?
Thanks in advance for any advice you can provide.
Neil.
N
 		Nir Frumer 4/25/2020

hi

I would put everything into 1 table

Now 2 options

  1. create a view for the requester without access to the "program" fields"
  2. use 1 access adding the "program" fields only to the edit page
    I think that both solutions will work for you, the decision depends on your preferences
    hope it helps,
N
 		nagate816 authorDevClub member 4/26/2020

Thanks for your reply. I may not have explained it clearly but the key is that for the Requester and program information they need to populate with data from a list of requester and for the program from a table with data about the program. I like your approach and will probably use it once I figure out how to populate the data. I have seen in other systems the concept of you select one value from a table (from say a lookup list) and then do a "lookup" to populate the data in the other fields. So I might pick a Program by it's name from a drop down list and then the next 10 fields on the form get populated with information from the other table with data about the program.

Thanks,

N~



hi

I would put everything into 1 table

Now 2 options

  1. create a view for the requester without access to the "program" fields"
  2. use 1 access adding the "program" fields only to the edit page
    I think that both solutions will work for you, the decision depends on your preferences
    hope it helps,
M
 		MikeT 4/27/2020

It should be possible to add an empty field to your query (a dummy field that's not part of the underlying table).

You can then format this field as a lookup-field that queries your lookup-table.

Then ist should be possible to populate your fields with values from the lookup table in an event, w.g. onChange.