DBPro Query the Results.
Quote from m.burdess on July 29, 2026, 12:08 pmCan someone explain How to show the results of a query shown in a Rectangle?
Lets explain, if the search show a number of people and you want to highlight one and show them with their family in a second Rectangle.
DBPro shows the fields variables that are needed to show this information, but how / where do I put the Query to show this data?
Can someone explain How to show the results of a query shown in a Rectangle?
Lets explain, if the search show a number of people and you want to highlight one and show them with their family in a second Rectangle.
DBPro shows the fields variables that are needed to show this information, but how / where do I put the Query to show this data?
Quote from mishem on July 29, 2026, 2:44 pmPerhaps the examples that come with DBPro can help you?
C:\Users\...\Documents\VisualNeoWin\NeoDBPro Sample Apps
Perhaps the examples that come with DBPro can help you?
C:\Users\...\Documents\VisualNeoWin\NeoDBPro Sample Apps
Quote from m.burdess on July 29, 2026, 4:14 pm@mishem
Thank you, but these do not cover this type of problem, as it is more complicated.
If was call the person Wiliam and give him an ID Number of 22 ( that is his birth ID), and was born in 1840 and died in 1916. In England we have a census ever 10 years, he can be found in the census from 1861 to 1911 ( that six line in table A ). This part is done, but the second part is the problem. In 1861 he living with this father, call William and two more , then starts his own family. So Williams ID 22 is linked to his Census number (that changes for each census), this works for part A, but what I need is to use is up to six parts from the database to link him with his family. And this will change for each of the six lines in part A. This is the problem, needing to read the information when highlighted in Table A.
Once again thank you
Michael
Thank you, but these do not cover this type of problem, as it is more complicated.
If was call the person Wiliam and give him an ID Number of 22 ( that is his birth ID), and was born in 1840 and died in 1916. In England we have a census ever 10 years, he can be found in the census from 1861 to 1911 ( that six line in table A ). This part is done, but the second part is the problem. In 1861 he living with this father, call William and two more , then starts his own family. So Williams ID 22 is linked to his Census number (that changes for each census), this works for part A, but what I need is to use is up to six parts from the database to link him with his family. And this will change for each of the six lines in part A. This is the problem, needing to read the information when highlighted in Table A.
Once again thank you
Michael
Quote from luishp on July 31, 2026, 11:57 am@m-burdess Michael,
I think this is a master-detail relationship rather than a query that must be placed inside the second Rectangle.
You appear to have something similar to this:
- A
CensusEntriestable containing William’s six census appearances.- Each record contains William’s
PersonIDand a differentCensusIDorHouseholdID.- A second table, such as
CensusMembers, containing all the people recorded in each census household.The important link for the second part is not William’s
PersonID. If you use that, you will only find William again. You need to link both tables using theCensusIDorHouseholdIDbelonging to the selected census record.DBPro has a specific command for this:
dbpDefineRelationship "FamilyDB" "CensusEntries" "CensusID" "CensusMembers" "CensusID" ""A complete simplified example would be:
dbpOpenTable "FamilyDB" "CensusEntries" "" dbpOpenTable "FamilyDB" "CensusMembers" "" dbpDefineRelationship "FamilyDB" "CensusEntries" "CensusID" "CensusMembers" "CensusID" "" dbpShowGrid "FamilyDB" "CensusEntries" "Rectangle1" dbpShowGrid "FamilyDB" "CensusMembers" "Rectangle2" dbpQuery "FamilyDB" "CensusEntries" "PersonID = 22"Now Rectangle1 should show the six census records for William.
When you highlight a different census record in Rectangle1, DBPro should automatically filter Rectangle2 and show only the family or household members whose
CensusIDmatches the selected record.You can also choose which fields appear in Rectangle2:
dbpDefineRelationship "FamilyDB" "CensusEntries" "CensusID" "CensusMembers" "CensusID" "Name, Relationship, Age, BirthPlace"The table and field names above are only examples. You will need to replace them with the actual names used in your database.
If your database does not currently store the same Census or Household ID in both tables, that relationship will need to be added first. Each household member must have some field that identifies the census household to which they belong.
@m-burdess Michael,
I think this is a master-detail relationship rather than a query that must be placed inside the second Rectangle.
You appear to have something similar to this:
- A
CensusEntriestable containing William’s six census appearances. - Each record contains William’s
PersonIDand a differentCensusIDorHouseholdID. - A second table, such as
CensusMembers, containing all the people recorded in each census household.
The important link for the second part is not William’s PersonID. If you use that, you will only find William again. You need to link both tables using the CensusID or HouseholdID belonging to the selected census record.
DBPro has a specific command for this:
dbpDefineRelationship "FamilyDB" "CensusEntries" "CensusID" "CensusMembers" "CensusID" ""
A complete simplified example would be:
dbpOpenTable "FamilyDB" "CensusEntries" ""
dbpOpenTable "FamilyDB" "CensusMembers" ""
dbpDefineRelationship "FamilyDB" "CensusEntries" "CensusID" "CensusMembers" "CensusID" ""
dbpShowGrid "FamilyDB" "CensusEntries" "Rectangle1"
dbpShowGrid "FamilyDB" "CensusMembers" "Rectangle2"
dbpQuery "FamilyDB" "CensusEntries" "PersonID = 22"
Now Rectangle1 should show the six census records for William.
When you highlight a different census record in Rectangle1, DBPro should automatically filter Rectangle2 and show only the family or household members whose CensusID matches the selected record.
You can also choose which fields appear in Rectangle2:
dbpDefineRelationship "FamilyDB" "CensusEntries" "CensusID" "CensusMembers" "CensusID" "Name, Relationship, Age, BirthPlace"
The table and field names above are only examples. You will need to replace them with the actual names used in your database.
If your database does not currently store the same Census or Household ID in both tables, that relationship will need to be added first. Each household member must have some field that identifies the census household to which they belong.