Detail avoiding 2 seperate TTable objects?

Anderson Franco

Delphi Developer

Sat, 06 Apr 2002 03:00:00 GMT

Master/Detail avoiding 2 seperate TTable objects?

Quote

>I want to create a Table (dBase or Paradox). Each record of this table
>should contain a subtable (4 string fields, 2 float fields, max 20
>records per subtable). To avoid having 2 seperate files I do not want to
>have the subtable as a seperate TTable object. Is there any possiblity
>to do this?

Christian,
Yes, its possible. But you are going to have a lot of work.
Master/detail tables are very very easier to develop.

Anderson Franco

John Elric

Delphi Developer

Sat, 06 Apr 2002 03:00:00 GMT

Re:Master/Detail avoiding 2 seperate TTable objects?

Why? If you are asking how to have a table be its own master detail, it is
very easy, use two TTable objects pointing to the same table, setup your
master detail relationship linking off your linkback key field.

John Elrick

Quote

Christian Laval <christian.la...@material.be> wrote in message

news:380C7046.AF562509@material.be...

Quote

> I want to create a Table (dBase or Paradox). Each record of this table
> should contain a subtable (4 string fields, 2 float fields, max 20
> records per subtable). To avoid having 2 seperate files I do not want to
> have the subtable as a seperate TTable object. Is there any possiblity
> to do this?

> Thanks!

> Best regards,

> Christian

Other Threads

1. Master-Detail Query w/Cached Updates requeries Detail when updating single fields in Master

2. Master/Detail w/SQL Server shows all detail records when inserting a new master record

3. Problem: Master/Detail shows details during Master Insert

4. which is faster using ttable or tquery in master detail form in SQL Server

5. TTable and a Master/Detail form

6. TTable master/detail performance problem

7. TTable-Master-Detail Question

8. TTable master/detail performance problem

9. Master-detail relationship with a TQuery and TTable...

10. TTable.DisableControls causes incorrect work with master-detail