3 replies
by oz_media
Access. I've seen a similar situation before that was due to filtering of records. The database must keep itself constantly indexed for fast lookups, when a filter is applied, it causes the server to rescan the indexes and delet records that don'tmeet the filter restrictions, thus slowing it down.
Ex: In ACT2000 (CRM not really a DB)the lookups are VERY fast unless the checkboxes for filtering notes are left UNCHECKED ie, 'Show types' has 4 check boxes. If one is left unchecked ie. 'e-mail', the server must rescan all the indexed notes and delete the ones that have an email field in them.
It's been a year since I worked with Access so I'm not sure on how the filtering works but I'm sure there is something similar there.
justmake sure that the record search criteria doesn't try to filter or eliminate items from a lookup unless needed. Even moving to the next record will be slow.
by carquiza
by ananthap
Specific points.
(1) In Access, it is necessary to COMPRESS the database when it is exclusively available. Particularly, if many users are adding data to it, this should be done regularly. Even daily night shift! 4000 client files. Definitely a lotof regular housekeeping seems necessary.
(2) Some oever-engineered Access and VB are like that. Thick client, lot of initial table and array building etc. seems a strong case for a rewrite.
end
This discussion is closed to new replies.
Trending Web Development posts
Sort by Trending