I am working on cached update master-detail and I have troubles...
My scenario: Master Table A with 3 details B C D, all in editable grids ; I
can scroll A (query) and must see B C D (queries); When I can start (what
event) BegincachedUpdates, if user can edit directly A, B, C, o D in grids
(without pressing any button o function key gor edit, but only Save and
Abort buttons) ?
Please consider that I have to edit and post always the master record (for
calc sum fields) if I edit, insert or delete a detail...
If I apply Updates, I must call another BegincachedUpdates for prepare the
reedit of the same records?
If I call BegincachedUpdates in afterscroll event of master table, I must
call cancelCachedUpdates and BegincachedUpdates in loop, or a new
BegincachedUpdates discard the old one? (it seems that they are
cumulative....)
I hope that you understand my (poor) english, sorry.
Good Job,
Stefano Monterisi

Stefano


This is three times you've posted the same question. I don't used cached updates so I can't answer. Please be patient and give people a chance to respond.

An alternative approach would be to email Tim directly since I suspect he will be the one to give you an answer.

Roy Lambert [Team Elevate]

Hi Roy,
yes, it's true. But because I see only this thread. The other two are NOT
visible for me in newsgroup.
Sorry,
Thanks
Stefano





"Roy Lambert" <roy@lybster.me.uk> ha scritto nel messaggio
news:815B9F2E-142E-4BCE-B55D-7E2D0F40C9D8@news.elevatesoft.com...
> Stefano
>
>
> This is three times you've posted the same question. I don't used cached
> updates so I can't answer. Please be patient and give people a chance to
> respond.
>
> An alternative approach would be to email Tim directly since I suspect he
> will be the one to give you an answer.
>
> Roy Lambert [Team Elevate]
>
>

Hi,
the true problem is that I cannot start editing directly in  a input field
and start BeginCachedUpdates on "Before edit" event because EDB internally
load all record in temporary table and move current record at the first one.
All problems may be solved if the BeginCachedUpdates "trasparently" don't
move focus from current edited record and field.
Otherwise I am constrain to force BeginCachedupdate operation on every
scrolling master table, also even if it don't need......
Thanks in advance,

Stefano Monterisi


"Stefano Monterisi" <info@sesamoweb.it> ha scritto nel messaggio
news:3A792382-5CC8-40C3-AC95-AA946E47F37F@news.elevatesoft.com...
>I am working on cached update master-detail and I have troubles...
> My scenario: Master Table A with 3 details B C D, all in editable grids ;
> I
> can scroll A (query) and must see B C D (queries); When I can start (what
> event) BegincachedUpdates, if user can edit directly A, B, C, o D in grids
> (without pressing any button o function key gor edit, but only Save and
> Abort buttons) ?
> Please consider that I have to edit and post always the master record (for
> calc sum fields) if I edit, insert or delete a detail...
> If I apply Updates, I must call another BegincachedUpdates for prepare the
> reedit of the same records?
> If I call BegincachedUpdates in afterscroll event of master table, I must
> call cancelCachedUpdates and BegincachedUpdates in loop, or a new
> BegincachedUpdates discard the old one? (it seems that they are
> cumulative....)
> I hope that you understand my (poor) english, sorry.
> Good Job,
> Stefano Monterisi
>
>
>
>

Tim,
please answer me;
I have rewritten login of an application using Anydac and Firebird, because
I need a lot of cached updates forms....
Please tell me what is your opinion on this...
(and don't forget to give us a timeline for monofile EDB databases)
Thanks in advance,
Stefano Monterisi


"Stefano Monterisi" <info@sesamoweb.it> ha scritto nel messaggio
news:984CE7C5-254A-4CC2-B0BF-3FC3BB6AC610@news.elevatesoft.com...
> Hi,
> the true problem is that I cannot start editing directly in  a input field
> and start BeginCachedUpdates on "Before edit" event because EDB internally
> load all record in temporary table and move current record at the first
> one. All problems may be solved if the BeginCachedUpdates "trasparently"
> don't move focus from current edited record and field.
> Otherwise I am constrain to force BeginCachedupdate operation on every
> scrolling master table, also even if it don't need......
> Thanks in advance,
>
> Stefano Monterisi
>
>
> "Stefano Monterisi" <info@sesamoweb.it> ha scritto nel messaggio
> news:3A792382-5CC8-40C3-AC95-AA946E47F37F@news.elevatesoft.com...
>>I am working on cached update master-detail and I have troubles...
>> My scenario: Master Table A with 3 details B C D, all in editable grids ;
>> I
>> can scroll A (query) and must see B C D (queries); When I can start (what
>> event) BegincachedUpdates, if user can edit directly A, B, C, o D in
>> grids
>> (without pressing any button o function key gor edit, but only Save and
>> Abort buttons) ?
>> Please consider that I have to edit and post always the master record
>> (for
>> calc sum fields) if I edit, insert or delete a detail...
>> If I apply Updates, I must call another BegincachedUpdates for prepare
>> the
>> reedit of the same records?
>> If I call BegincachedUpdates in afterscroll event of master table, I must
>> call cancelCachedUpdates and BegincachedUpdates in loop, or a new
>> BegincachedUpdates discard the old one? (it seems that they are
>> cumulative....)
>> I hope that you understand my (poor) english, sorry.
>> Good Job,
>> Stefano Monterisi
>>
>>
>>
>>
>
>
>

Stefano,

<< the true problem is that I cannot start editing directly in  a input
field and start BeginCachedUpdates on "Before edit" event because EDB
internally load all record in temporary table and move current record at the
first one. All problems may be solved if the BeginCachedUpdates
"trasparently" don't move focus from current edited record and field.
Otherwise I am constrain to force BeginCachedupdate operation on every
scrolling master table, also even if it don't need...... >>

This is the nature of the data-aware controls and has nothing to do with EDB
specifically.  BeginCachedUpdates isn't doing anything special other than
notifying the dataset that the records have changed, which is correct and
the proper thing to do since the records *may very well have changed*
between the last time they were loaded and when the cached updates were
started.

If some other database front-end isn't doing this, then it isn't handling
this correctly for a live dataset, or it is already statically caching the
records in an optimistic fashion, which would be the equivalent of
BeginCachedUpdates on every change of the master record.

--
Tim Young
Elevate Software
www.elevatesoft.com

Ok, Tim.
I intend a different way.... a "delta" parallel table that start when I call
BeginCachedUpdates or similar (StartDelta) on start editing. From this
moment delta contain only modified fields (on exit editors) and records, and
can be applied  to the real table... but without recall/update/refresh
anything in the meantime...
I have to use memory tables or Anydac (that don't have EDB driver, so FB
)  for obtain the result I want ...
Good Job,
Stefano Monterisi