If using an Microsoft Access frontend linked to SQL backend and in the event that the SQL server is down the user would like to look at the data (or as close to the current data as possible).
Solution - Create a DTS package in SQL scheduled to run daily exporting the information to a local Microsoft Access Database. Make sure you include the "create and drop" option - so the tables don't duplicate the information but refresh the local Access database with the current updates. With this in place if the SQL server is down the user(s) can view yesterday’s information (which is all stored locally in an access database). This should help until the live SQL server is back up and running.
Note - you might only want to select critical tables due to the size of the data being locally stored in the access application.
Solution - Create a DTS package in SQL scheduled to run daily exporting the information to a local Microsoft Access Database. Make sure you include the "create and drop" option - so the tables don't duplicate the information but refresh the local Access database with the current updates. With this in place if the SQL server is down the user(s) can view yesterday’s information (which is all stored locally in an access database). This should help until the live SQL server is back up and running.
Note - you might only want to select critical tables due to the size of the data being locally stored in the access application.