Greetings,
We're currently running office/access 365 the db is deployed in split (be/fe) environment. We have a provider table w/ almost 80k records. The way the db is designed (by someone else), or supposed to work is as follows:
Whenever users create a new case, a search window appears asking them to enter (provider name, provider number etc.) to see if the provider already exists, if the provider exists, then they will select it and update the remaining information. If the provider doesn't exist, then users will be prompted that "can not find provider... would you like to create a new provider?" then users click Ok to create a new record.
I'm not sure this is due to the fact that we have over 65k records, to search thru, but this process (the search) has been too slow i.e. spins forever, freezes up etc.
Now, I'm tasked to update the current provider table with the latest list that is saved in excel file.
1. If I move on with the update, is there a better approach for the workflow?
I learned access can handle more than 65k, but what to look is how big the db is etc.
2. Since the db is split, I checked properties of the back end (tables) and noticed 780MB, is this the correct way to identify how big the db is?
TIA
Regards,
We're currently running office/access 365 the db is deployed in split (be/fe) environment. We have a provider table w/ almost 80k records. The way the db is designed (by someone else), or supposed to work is as follows:
Whenever users create a new case, a search window appears asking them to enter (provider name, provider number etc.) to see if the provider already exists, if the provider exists, then they will select it and update the remaining information. If the provider doesn't exist, then users will be prompted that "can not find provider... would you like to create a new provider?" then users click Ok to create a new record.
I'm not sure this is due to the fact that we have over 65k records, to search thru, but this process (the search) has been too slow i.e. spins forever, freezes up etc.
Now, I'm tasked to update the current provider table with the latest list that is saved in excel file.
1. If I move on with the update, is there a better approach for the workflow?
I learned access can handle more than 65k, but what to look is how big the db is etc.
2. Since the db is split, I checked properties of the back end (tables) and noticed 780MB, is this the correct way to identify how big the db is?
TIA
Regards,