----- Original Message -----
Sent: Thursday, October 26, 2000 1:23
PM
Subject: Re: [DUG]: Flagging invoiced
records
OK
I have now implemented Dave's suggestion and it
works well (once I remembered to set the seconadry index name!)
It sped up the report on my machine from almost 2
mins to under 3 secs.
(Thank you David's)
The client machine must have a performance
problem because it was apparently taking them 30 mins for the same report from
a similar sized database.
Mark
----- Original Message -----
Sent: Tuesday, October 24, 2000 5:26
PM
Subject: Re: [DUG]: Flagging invoiced
records
It's hard to say without more information but
if you are processing a lot of invoices in each print run then I would say
that running your own prepared update queries for each row you want to
update (as suggested by David O'Brien) is probably the fastest way of
solving your problem.
Of course that means that you are updating the
database directly bypassing MainDataModule.DocketsTable. As a result
MainDataModule.DocketsTable will become outdated and need refreshing,
probably by closing and re-opening (or using the Refresh method?) when
you are finished the print run. The cost of this will somewhat negate the
gains you make from running direct update queries but I suspect it would
still be a lot faster.
David.
DB Solutions.
----- Original Message -----
Sent: Thursday, October 26, 2000 9:10
AM
Subject: Re: [DUG]: Flagging invoiced
records
Dave
Yep, I have a unique composite (3 field)
key.
I'll try FindKey
Thanks
Mark
----- Original Message -----
Sent: Tuesday, October 24, 2000
3:59 PM
Subject: RE: [DUG]: Flagging
invoiced records
If you have a unique field on the table, return that in the query
and do a findkey on the table. Or write an update query rather than
using a filter.
Dave.
