After having half the data on the database going missing twice, our fearless leader decided that Microsoft SQL Server Replication will not be used.
So now I will attempt to re-write the Replication part using just Visual BASIC, ADO, and whatever I can figure out to copy from one database to another and update the data. This is a trick that even Microsoft, IBM, and other companies have not figured out how to do. Not Replication, but more like Synchronization like a PalmOS device does. Hospital Server has data, our Server has data. We make a change on ours, it gets sent to theirs. They make a change on theirs, it gets sent to ours. We won't always have a connection to their LAN. Some of them have a dial-up, others an encrypted connection and the key changes every 15 seconds to connect to it, and yet others have a VPN that we have to manually connect in order to connect to their network. So SQL Server Replication will not work here, I will have to make a custom VB program to do the Data Copy for them, So simple that they just make the connection, set up the UDL files to point to the Hospital database on our server and the Hospital database on their server, and then they just press a button and start the Data Copy.
Brain Surgery, Rocket Science, Quantum Physics, all child's play next to this. Wish me luck.