This is a general desing question. I have a project which involves a front / back end database (both access 2K). The back end resides on a server on "network #1"
Due to some pretty strict security settings in our organization, we also operate "newtork #2" This is the "secure" network, which requires swapping hard drives, different logon names, separate network hardware, etc. There is NO way to migrate data from #1 to #2, except by way of disk, removable drive, etc.
I have a project on the secure network (#2), that needs to be able to import one table from my backend on the unsecure network (#1), over to the secure network (#2). I can think of several possible ways to do this, and would greatly appreciate some guidance on what would be the best way. The circumstances:
1. Data will only be modified on network #1 (unsecure), so I really need to just import and overwrite the existing table.
2. I can barely fit the table on a diskette, so will probably use a ZIP disk for transferring the data. Our organiztion uses USB ZIP 250's, which may or may not have the same drive letter depending on which computer they are installed in. So I need to be able to browse for the file both when importing and exporting.
3. Due to some pretty complicated design issues in the application, I would prefer to stay away from replication. I believe (but could be wrong here) that since I don't need to update data once it is moved, I really won't realize any benefits from replication. I really only need this one table to be transferred, and other than the single table, the two applications share no other characteristics, so I think replication will not suit this situation well.
4. I need to be able to essentially replace the table in network #2 with the new one. I don't want to add records to the data already there.
Any thoughts?
Due to some pretty strict security settings in our organization, we also operate "newtork #2" This is the "secure" network, which requires swapping hard drives, different logon names, separate network hardware, etc. There is NO way to migrate data from #1 to #2, except by way of disk, removable drive, etc.
I have a project on the secure network (#2), that needs to be able to import one table from my backend on the unsecure network (#1), over to the secure network (#2). I can think of several possible ways to do this, and would greatly appreciate some guidance on what would be the best way. The circumstances:
1. Data will only be modified on network #1 (unsecure), so I really need to just import and overwrite the existing table.
2. I can barely fit the table on a diskette, so will probably use a ZIP disk for transferring the data. Our organiztion uses USB ZIP 250's, which may or may not have the same drive letter depending on which computer they are installed in. So I need to be able to browse for the file both when importing and exporting.
3. Due to some pretty complicated design issues in the application, I would prefer to stay away from replication. I believe (but could be wrong here) that since I don't need to update data once it is moved, I really won't realize any benefits from replication. I really only need this one table to be transferred, and other than the single table, the two applications share no other characteristics, so I think replication will not suit this situation well.
4. I need to be able to essentially replace the table in network #2 with the new one. I don't want to add records to the data already there.
Any thoughts?