Switching between tables

psuplat

Registered User.
Local time
Today, 16:21
Joined
Mar 18, 2009
Messages
35
Hi everyone,

not sure if what I want can actually be achieved but here goes,

i have a db system used on a fast production line, that works of linked tables located somewhere on the network.

What I was thinking to do is something that keeps the system working even if the network goes down.
Let say there is a second, small database placed on local drive with relevant tables. When the form responsible for inputing of data into the main table cannot do it (eg. due to network issues) it switches to a table in local database.

Does that make sens? is something like that possible at all?

Thanks for any info
 
Well, yes. To a limited extent.

If your database can continue to record new data without refering to the existing data (i.e. no lookup tables are inaccessable, etc) then you could theoretically have temporary local versions of the tables to basically use as a cache and upload to the server at a later date.

However the only way I can even consider something like that is with a lot of VBA code spread throughout the database. Ideally the database will need to be continually checking the connection so it knows when to switch tables, which could also cause performance issues.

It would be one hell of a job. A better solution may be to have a second, stand-alone copy of the database with internal tables for use during network downtime. You could set the database to send an email to a set email address to confirm when it contains data and once the network is available again someone can transfer the data (which can be done via append queries rather than manually).
 
what's the idea of taking the network server down ?
as I see it a network server should work 24/7
 
If your local system can be made to run by itself, then it seems a better tactic would be to let the local system run locally full time. The local system, now and then, could update the central db with data. If that fails, no biggie, a new update could be attempted 30 seconds or minutes or whatever, later. All that provided that no current data from central location are needed to run locally.
 

Users who are viewing this thread

Back
Top Bottom