I have a Access 2007 (Office 2010) database which I recently split. The back end is located on a server in a shared folder. The front end is located on each end user's local drive and is synchronized with a master copy each time the database is opened.
The database has a main member's form (frmMembers). It is bound the the main table (tblMembers). On the main form is a command button that opens a custom search dialog. This dialog has an option group to force the user to select a search criteria (phones, names, addresses, etc.). The user chooses a search (usually phones) and begins typing in the search edit box. As soon as the user begins typing, a list of matching criteria begins to appear in the search results window. The more information they type, the more the search is narrowed.
This is where it has become "painfully" slow. I suspect that the problem is the way the database is locking the back end? I've tried creating a simple, one-record table and binding it with a hidden form, that runs hidden the entire time the database is open, but no luck.
I have attached the custom dialog code, so that possibly, one of ya'll could take a look and come up with a more efficient solution? Create a recordset and search that versus the main table? Please help. The client is driving me crazy!