Suppose I have a multi-user shared-data app with potentially huge
tables (20+MB). With this app the larger tables contains important
data which requires them to be refreshed frequently. This causes
performance problems. I was thinking of reducing this by using an ini
file in the data path to record when a table has been modified. When
the table needs to be refreshed, check the shared ini file to see if
the table has been modified since the last check. Only refresh if it
has been modified. Good idea or no?

Of course it would even be better if you could somehow correlate the
changed records with the subset that relates to the current situation
in the app. For example in a billing app, refresh only if any records
related to the invoices being viewed have changed.

___
Free Project Time Tracker for Delphi Developers
http://www.cybermatrix.com/pcdelphi.html

Michael

I would use another table to do that instead of INI file (easier than)
because you will have to deal with file locks, wait for locking, and etc,
things that a simple table already does internally.

Eduardo

"Michael Fullerton" <fullerm@spamkiller-remove-cybermatrix.com> escreveu na
mensagem news:unc9t21cnk9v587a1vhl2v1fd5fioht51e@4ax.com...
> Suppose I have a multi-user shared-data app with potentially huge
> tables (20+MB). With this app the larger tables contains important
> data which requires them to be refreshed frequently. This causes
> performance problems. I was thinking of reducing this by using an ini
> file in the data path to record when a table has been modified. When
> the table needs to be refreshed, check the shared ini file to see if
> the table has been modified since the last check. Only refresh if it
> has been modified. Good idea or no?
>
> Of course it would even be better if you could somehow correlate the
> changed records with the subset that relates to the current situation
> in the app. For example in a billing app, refresh only if any records
> related to the invoices being viewed have changed.
>
> ___
> Free Project Time Tracker for Delphi Developers
> http://www.cybermatrix.com/pcdelphi.html

Michael,

<< Suppose I have a multi-user shared-data app with potentially huge tables
(20+MB). With this app the larger tables contains important data which
requires them to be refreshed frequently. This causes performance problems.
>>

A refresh in DBISAM only involves checking the table header to see if
anything has changed, so it doesn't actually refresh anything unless
something has changed in the table.

--
Tim Young
Elevate Software
www.elevatesoft.com