While I am not sure what the specific error will be (simple failure to copy the db because it's open, connection drop due to Win2K file locks being present, db corruption, etc), I would have to say that it would not be successful. Is there any way that you can batch run a backup and sync that? Most current db systems (like MS SQL) have many methods of syncronization that can be done in different ways, like nightly backup and sync jobs or transaction-based where it will update the slave database after each successful transaction. Also, are you using master-slave or merge syncronizations? The backup and transfer method would work much better with master-slave than with merge (and may not work at all on many db systems).

Thanks clutch, I must confess that this isn't my first line of computer work, I'll pass on the advice to the person that's asked me, I think the biggest drawback is going to be that the database application is an old (old old) program, the guy reckons it runs in NT4 olay, so maybe It'll become clearer when we look at it later.
 
Cheers