Actually, I think my solution is denormalized because you have repeating information in multiple records. In general [I know your child has fixed 3 records per parent record], what you ask for is not practical in a 1-to-unknown-many because you would first have to determine how many extra fields you need based on the max number of child records for any 1 of the parent records. There is no single SQL to do what you want that would create a SQL view in VFP.

If the fields from the child table are numeric, I have a solution that takes multiple SQL statements. With character data, I see no solution to what you want except maybe GenXTab, but that is still not a SQL solution.