I wish to make use of cached updates.  My reading of the manual leads me to
think what you need is:

datasource - > client dataset -> dataprovider -> dataset.

I have two Paradox 4.5 tables, Ordmast, Ordetl local on the machine.  I wish
to link them master detail

I set up:
Ordmast DBEdit fields -> datasource - > client dataset -> dataprovider ->
dataset.
Ordetl DBGrid -> datasource - > client dataset -> dataprovider -> dataset.

and got the data showing on the form but when I link them master / detail
the data doesn't show up properly in the grid.

Everything's active, fetchupdates is enabled etc.

The hook up fine under a conventional datasource -> dataset configuration.

1. Any ideas?
2. Are cached updates difficult to implement?  It sounds like an easy way of
providing an undo feature on table edits etc.

Thank you

Warren

---------------------------------------------------------------
Pearson Technical Services
pearson...@earthlink.net
ph / fax 818 360 2600
mobile 818 359 4717

Are the datasets TTable or TQuery? If you are using TQueries, what is the
SQL statement? How are you creating the master/detail link? I assume you are
using the MasterSource and MasterFields properties of the ClientDataSets.

--
Bill
(TeamB cannot answer questions received via email)

The datasets are TTable.

Yes I am using the MasterSource and MasterFields properties of the detail
tables ClientDataSet (2c.) to point to the datasource of the master table
(1b).

1a.Ordmast DBEdit fields -> 1b. datasource - > 1c. client dataset -> 1d.
dataprovider -> 1e. dataset.
2a. Ordetl DBGrid -> 2b. datasource - > 2c. client dataset -> 2d.
dataprovider -> 2e. dataset.

Regards

Warren

"Bill Todd (TeamB)" <bill.nos...@dbginc.com> wrote in message
news:3b61a1d1_2@dnews...

I notice that you said that data does not "show up properly" in the DBGrid.
Can you explain what you mean by that?

--
Bill
(TeamB cannot answer questions received via email)

For example, the first master table record has about 12 related detail
records.  When I run it linked master/detail I may get the first part of the
key field out of the detail table on the top row of the grid only. (the
detail key is OrderNumber, ItemNo  - so I would see just one OrderNumber -
kind of like it forgot to blank that out)  I can navigate the master table,
scrolling to new records with no change reflected in the detail table.

Thank you for your interest in helping me with this.

You haven't commented to date on the relative complexity of managing a
cached update relationship.  Is it a headache or does it work pretty
smoothly?

Thanks

Warren

"Bill Todd (TeamB)" <bill.nos...@dbginc.com> wrote in message
news:3b6218cf$1_2@dnews...

I am not sure what is causing the problem you describe. I have never tried
using ClientDataSets with TTables. If you want to use ClientDataSets as a
substitute for cached updates the best thing to do is use TQuery's and make
the detail table a nested dataset. This is described in the Developer's
Guide.

--
Bill
(TeamB cannot answer questions received via email)