Hi
I have a database that has 150 users all with there own front end on a laptop, because they need to use it offline they 'upload' to a core database when they connect to the network once a week.
I have an issue that when i compact & repair the 'core' database, the individual front ends error when they try to sync with the core and get a halt message.
They have a button on a maintence tab with a button to compact and repair, once they run it there end the sync works. It is not very user friendly that when i compact the 'core' that they need to run a compact and repair everytime they go to sync if they error.
It is impossible to deploy another database to the 150 users at the moment but obviously getting 150 phone calls on a friday is not ideal
it obviously due to a non-compact and repaired database trying to connect to a compacted and repaired one, any suggestions would be great.
Thanks
I have a database that has 150 users all with there own front end on a laptop, because they need to use it offline they 'upload' to a core database when they connect to the network once a week.
I have an issue that when i compact & repair the 'core' database, the individual front ends error when they try to sync with the core and get a halt message.
They have a button on a maintence tab with a button to compact and repair, once they run it there end the sync works. It is not very user friendly that when i compact the 'core' that they need to run a compact and repair everytime they go to sync if they error.
It is impossible to deploy another database to the 150 users at the moment but obviously getting 150 phone calls on a friday is not ideal
it obviously due to a non-compact and repaired database trying to connect to a compacted and repaired one, any suggestions would be great.Thanks
