![]() |
HJB 12/24/2019 |
Hello all... I am working on a database to catalog serious injury or fatal vehicle crashes. My goal is to be able to easily find similar crashes to use as a guide for future investigations. For example, if we are investigating a fatal crash involving a motorcycle, I want to search the database for other crashes in which a motorcycle was involved. I have one table for basic data about the crash
|
D
|
druck281 author 12/25/2019 |
Think, a MASTER/DETAIL oriented database design is what is fitting the needs. For example, MASTER table to contain the "Flagnames" while DETAILS table is holding the rest of the data. As PHPRunner provides SEARCH and ADVANCED SEARCH by default, finding of what you need is not a matter to brain about at all. Once CHECKBOXES are used in a table, you shall see ALL of them, both, the checked and the unchecked ones anyway. https://xlinesoft.com/phprunner/docs/master-details.htm
|
![]() |
Sergey Kornilov admin 12/25/2019 |
If you are looking to implement master-details relationship check this article first: |
![]() |
HJB 12/26/2019 |
If you are looking to implement master-details relationship check this article first: https://xlinesoft.com/blog/2011/02/28/how-to-setup-many-to-many-relationships/ Basaically many-to-many relationship is a set of two master-details relationships.
|
![]() |
HJB 12/26/2019 |
If you are looking to implement master-details relationship check this article first: https://xlinesoft.com/blog/2011/02/28/how-to-setup-many-to-many-relationships/ Basaically many-to-many relationship is a set of two master-details relationships.
|
D
|
druck281 author 12/31/2019 |
https://imgur.com/a/Vf0SYdI - IMGUR uploaded screenshots of 1st draft based ADD and LIST page dummy records For inspiration purposes. Sure, your wished MANY-TO-MANY web app design would finally work, while my personal focus is USABILITY and ERGONOMICS in first instance, here on DATA COLLECTION and CLASSIFICATIONS, especially in times where it more and more happens that SMARTPHONES are used for same..., so the screen content should be tiny, with built-in links (calendar, add new functionality). Thanks to BOOTSTRAP technology inside PHPR, optimal display on smartphones/tablets does not need manual coding. Since lots of Search and Report Features inside PHPR v10.3 are shipped by default, at least me is seeing no problem to get any client satisfied on fact finding missions or reports results to be seen, either of cumulative or cross-tab shape. If MANY-TO-MANY is definitely a MUST have, a MASTER / DETAIL design can be added to the above dummy design anyway.
|
![]() |
HJB 12/31/2019 |
@druck281 - It's a SINGLE page rather than a Many-to-Many issue while however, if wished, a Many-to-Many ADD-ON via Master/Detail could be attached, if needed. Give me a PM via this forum and I shall send you my PHPR v10.3 project file along with the SQL Dump file to let you import the database structure, all FREE OF CHARGE, for your further studies and development of your project as I'm currently on another 2020 course of projects where design & production of web appliances are no longer mattering at all, say, I shall drastically reduce my forum presence in 2020 anyway as it came to light that web appliance development can be no longer a "bread and butter" business for me at all. HTH and "Happy New Year". |
![]() |
HJB 1/1/2020 |
So far, no PM received yet. |
D
|
druck281 author 1/5/2020 |
@walk2fly...You were right on. After your advice about using the Master-Detail relationship instead of trying to do a Many-many, I had it working on the add page but not on the edit or view pages. I looked at the Project file you sent me and found that I had the settings correct but I was still in 10.2. Once I upgraded to 10.3, it worked perfect. |