Hi Pascal,
I won't ask you for a reason to build such an application.
However, if it is possible to change the database structure I would add some
sort of timestamp field that changes on insert/modification to each table
you want to track.
So you would track only whether max(timestamp) has changed or something like
that - this will cover inserts and modifications.
As per deletes, I would rely on combination of count(*) and timestamp.
--
Miha Markic [MVP C#, INETA Country Leader for Slovenia]
RightHand .NET consulting & development
www.rthand.com Blog:
http://cs.rthand.com/blogs/blog_with_righthand/ [quoted text, click to view] "Pascal" <mattia.pascal@gmail.com> wrote in message
news:1177778738.160641.18390@n76g2000hsh.googlegroups.com...
> Hi everybody,
> a suggestion, please. I have an application A that modifies the
> records of an access database. I should write an application B
> (running on the same machine) that monitor these changes, without
> modifying application A. I think the only solution is polling the
> database and check every record in the table. I realized an
> application that reload periodically in memory all the records (I use
> an oledbdatareader, stayng always connected) and compares them with
> the previous loaded records. Unfortunately the database is very
> large
> and this procedure takes 2s on a Pentium IV. Do you know any better
> method or some tips I could use to improve the performances? I tried
> using a dataset and working disconnected, but it's slower (3s).
> Thanks.
>