You could try changing the recordset type on your form to snapshot - you won't be able to change data but you may find the filter works more quickly.
Also, another thing about my way of working - it blends the quickfind filter with the filter created using the access filtering So say Ii wanted all customers with 'smith' in their name and a postcode beginning 'DE' I can do this by using quickfind for smith and then use the access filter for the postcode. (Of course you can just use the access filter in this scenario)
I can then save the filter string in a table to be called back up as a 'previous filter' or when the form is reloaded.
I'm not saying other routines don't do the same, just this meets my functionality requirements
Thanks CJ_London... i tried your suggestion about snapshot. when i changed it to my recent database it cant give result i dont know what happened but when i did it on my older database (less function, less data) it is working though still the slow motion is still there.
i dont get about the second suggestion. im not really an expert with Access, im just a beginner. i research and apply the things i learned. im just new to Access. im not even a programmer but i can understand if i can focus and give time to it.
i think there would be no solution for the "slow motion" effect database since i have lots of data stored plus with calculations. what i have in mind right now is to create a BUTTON named SEARCH that the user will click that button once they decided what word to search on the database because right now, once the user key-in or type a letter/word the database start searching (that goes with the calculation also) which makes the database soooo slow. if there is a SEARCH BUTTON i guess it will lessen the problem. this SEARCH BUTTON lets the user type in the complete word/s once done they will press the button and thats the time the database will search, calculate, and give results. unlike what i have now, every key stroke the database will search, calculate, and give results. so, how can i create a SEARCH BUTTON? i know how to create a button but how this button will function or give result, please help.
my database is from John, i just made some changes and additions but most likely the same:
http://www.access-programmers.co.uk/forums/showpost.php?p=1182790&postcount=4
NOTE: John's database works perfectly because it has less data, no calculations, and less functions than mine.