here's the situation of my database. it handles 2 things - allows users to input their work time, and allows users to check codes.
for users to input their work time it's quite simple. it's inputting something from nothing so they enter all the inputs from their head / the time they start work till the time they end.
for users to check the codes, they first need to "download the codes" from the main replica --> or rather the right term is to synchronise the data containing the codes, and then later on after they have checked the codes they need ot synchronise the databack to the main replica on the network drive.
synchronisation takes time and synchronising the DB on opening and on closing makes the user feel that it's very "slow" --> when i open the DB i have to wait for 3 minutes. synchronising on closing is not that bad, but on opening is something i need to avoid.
so my DB is split into FE and BE and the replicas is only the BE.
when the user keys in their work time, it goes from the FE to the BE on their local machine. then when the user wants to check the codes (right after entering their work time) they need to sync the BE from the network replica.
is there any way that i can allow users to enter their work time whilst i sync the BE too? so this gives them a feeling of programme responsiveness. something like a doevents function, but the thing here is that it's using both the same BE.
is it possible for me to have a main replica BE and 2 child replica BEs which it syncs to? the 1st child BE will just contain the work hours and the 2nd BE will contain all the codes to check.
what do you think is the best way for me to do it? thanks guy!!
i'm thinking maybe the only way is to have a sync button - such that user opens the DB, it's fast and zippy, and after they enter their work time, they hit the sync button and then they expect it to "stall" for 3 minutes. so it's handling the users expectations. but i would prefer to be able to do it whilst the user is entering their work time. thanks guys!!!