A local company has a new server, and wants to use the old server as a backup domain controller. This company has about 20 Access databases and several VB applications referencing those db's. All were written by employees that are no longer there. The manager wants all of the code to read and write to an identical duplicate of each database on the second server AT THE SAME TIME as writing to the first primary server. At first, I thought this wouldn't be that difficult. Just set new database references pointing to the second server also, and add a few lines here and there. However, the more I think about it, the more mind-boggling it gets. What about references to currentDB, dlookup functions, linked tables, etc.?? Using the exact same Access mdb or VB app on EITHER server, and having it write to both servers simultaneously is not going to be very easy, I am finding out. I have been thinking about replication, or just copying the Access tables from server 1 to server 2 periodically, but the manager has it in his head that his method of writing to both simultaneously is the way he wants it done. I have never done anything with replication. Does anyone have any thoughts or suggestions?? If you do and this is possible, I will be willing to hire someone to assist me.
Right now, I am just looking for guidance. If it turns out to be just a matter of time-consuming code-writing, I will be willing to hire someone to assist me.
Servers are Windows 2000. Most workstations running the apps are NT 4.0 or Windows 2000.
## Deadline information
Initially, I would like responses to determine if this is feasible at all. If so, I would like to have someone assist me within the next few weeks.