"the updatestatus procedure will just kill your performance !"
No it won't. You never ran the code or you'd have seen that it simply shows a pre and post update, not during, so that does not slow anything down. It is simply there as a timestamp to show how long each individual process took in total. Also, ADO is not the issue. Again, running the application would have proved that.
I truly appreciate you taking the time to comment, but will wait for other relevant comments.
Thanks.
Main Topics
Browse All Topics





by: Geert_GruwezPosted on 2009-06-15 at 14:36:12ID: 24633272
performance ?
le/
um, with this code ?
probably not ... why ?
you seem to be wanting feedback about everything your code does
this is ok in test, but throw it away if you want speed
the updatestatus procedure will just kill your performance !
so get rid of that for starters
second you aren't using the fastest components on earth ... ADO ?
consider testing it with SDAC from www.devart.com
and while you test that, did you notice they have a virtual memory table ?
http://www.devart.com/vtab
in my opinion try and minimize the screen routines
instead writing to a log file is a lot faster (though this also slows down with a virusscanner)
when updating data try disablecontrols / enablecontrols
Select allOpen in new window