ACC: Overnight Batch Considerations and Sample CodeLast reviewed: August 29, 1997Article ID: Q125772 |
The information in this article applies to:
SUMMARYAdvanced: Requires expert coding, interoperability, and multiuser skills. As your use of Microsoft Access increases, you may find it necessary or convenient to run some of your Microsoft Access processes at night or at other times when you are absent. This article describes how to run Microsoft Access processes at specified times without user intervention. This article assumes that you are familiar with Visual Basic for Applications and with creating Microsoft Access applications using the programming tools provided with Microsoft Access. For more information about Visual Basic for Applications, please refer to your version of the "Building Applications with Microsoft Access" manual. NOTE: Visual Basic for Applications is called Access Basic in Microsoft Access versions 1.x and 2.0. For more information about Access Basic, please refer to the "Introduction to Programming" manual in Microsoft Access version 1.x or the "Building Applications" manual in Microsoft Access version 2.0
MORE INFORMATIONPart 1 of this article includes sample code that starts two update queries. One of the queries is started at 11:00 P.M. and the other is started at 4:00 A.M. the next morning. In this example, you start the code by clicking a command button. Part 2 contains a sample decision-support flow chart that details some of the processes and decisions you might use for unattended operations. You may want to use other graphic aids or decision-support software to represent your scenario.
Part 1: Steps to Produce Sample Job Stream
Part 2: Sample Overnight Decision ConsiderationsThe following considerations are for illustrative purposes only. You must carefully consider how and when to process your own data. You should test critical processes against test data before implementing unattended processing. Note that contingency procedures are especially important if follow-on processing must proceed early in the day. You may want to use transaction processing to handle sets of processes that must succeed as a group or be rolled back to a starting point. You may want to use Microsoft Project or other decision-support software to graphically represent your critical path to help you understand how to proceed in partial failure situations. Sample Overnight Decision Flowchart:
Do critical daily activity processes needed by tomorrow or ASAP (backups, accounts receivable, patient status, and so on). If critical processes fail? THEN Call or page primary responsible person or secondary responsible person or management. If some or all critical processes continue to fail or help is slow in arriving? THEN Run processes not dependent on previous failures. Else Continue to analyze the problem and wait for help. Else Do any remaining daily activity updates. Do nightly backups after updating. (It is your business decision whether to back up your data before or after nightly processing, or both before and after.) Do reporting. Do user-specific batch SQL requests. Upon returning, check status of processes. REFERENCESFor more information about transaction processing, search the Help Index for "Transactions, processing." For more information about using loops, search the Help Index for "Loops."
|
Additional query words: archive
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |