AP: Trouble-Shooting with Tom van Stiphout and Kim Young
315 بار بازدید -
2 ماه پیش
-
Tom and Kim draw on
Tom and Kim draw on decades of experience creating and troubling-shooting Access applications. Learn what you and should be doing to avoid problems and deal with them if they occur.
They explain principled approaches to avoiding, identifying , and resolving problems. Numerous examples of real-world incidents are scattered throughout the presentation.
Links in the video:
DISCORD SERVER & Invitation to Join
Discord: discord
Discord: discord
Article ODBC (URL is Case Sensitive)
https://www.accessmvp.com/TomVanStiph...
Table of Contents:
00:06 - Intro Tom van Stiphout and Kim Young
00:25 - Access News and announcements
00:38 - Visit the Access Roadmap for new features
01:24 - Join the Access Discord Server and hang out with other Access developers
03:08 - New and revitalized AUG chapters
07:28 - Begin the presentation
07:40 - We're in Trouble (music)
08:58 - Different Kinds of Error Messages, what do they look like and why
09:10 - 1. An unhandled Accdb error
09:12 - 2. A basic MsgBox for errors
09:22 - 3. A rich, informative custom error message
09:40 - 4. An Unhandled error from an accde
09:55 - 5. Third-Party Error Handler -- VB Watchdog
10:53 - Check the Windows Event Error log with deep technical detail
11:32 - Link to article "Handling ODBC Errors" - Tom van Stiphout
14:15 - Be aware that environmental changes can cause failure, e.g. network interruptions
14:58 - Be aware of potential MS Update and Bug Releases
15:10 - When posting bugs to online forums, the details are important
18:02 - If it's an update bug, try 1st to roll back MS update to last working version
19:09 - Planning and Rehearsal of your recovery plan are essential to prepeare for emergencies
21:04 - Defense Steps at Runtime, when a failure occurs
21:09 - Make backups and store them safely
21:50 - Can you replace a bad FE and trouble-shoot the problem later?
22:44 - Use Task Manager to isolate hidden instances of programs that may be running
23:09 - There is minimal debugging available in accdes
23:30 - Is the error reproducible? Has it been reported online by others?
23:51 - Demo of standard tools using Northwind Dev to show techniques
24:36 - Using the Watch Window in VBE
25:46 - Reviewing the Call Stack for complex processes
27:00 - Debugging in accde is possible in the Immediate Window with proper advance preparation
27:56 - Identify Current Screen and active control and active control values
28:08 - Inspect the state of a running form
28:30 - Pre-placed debugging tools for more extensive review of code
31:06 - Inspect ASCII strings in immediate window
32:20 - DumpRecordset to inspect records
35:44 - Design Time Considerations
36:11 - Defensive programming that anticipates as many possible problems as possible
36:52 - Choose the apropiarte Update Chanel for production applications--Not Current Channel
37:35 - Balance your tolerance of risk with availability of new or improved features in an update
37:52 - Have a "Scout" working on a proof of concept computer on the Monthly Channel to prepare for upcoming changes
38:22 - Implement and use consistent error handling
40:03 - Plan what to track and log to improve user feedback
40:43 - Error logs are a source of valuable information on crashes
41:28 - Design and describe a deployment procedure and execute it!
42:06 - Validate deployment in progress, before and during, don't wait until after
42:56 - Development Discipline produces reliable results
43:13 - App tables to document the current database structure
45:23 - Third-party tools are also available
48:25 - Set aside time to improve your knowledge
52:49 - Consolidate code to improve reliability and maintainability
52:57 - 3 Tier app design,
Data
Logic
Interface
53:15 - Common code belongs in a stand alone module, not repeated in forms
53:51 - Debug.Assert to identify 'unknown else" code at design tme
54:19 - Design time tool rather than runtime error handler
55:36 - Deug.Assert to test incoming parameters, avoiding data and datatype errors
56:39 - Doing nothing has a cost
57:58 - Keep track of known MSFT Bugs like DatePart()
58:44 - Use helper tables, such as a table of dates for example
59:44 - Steps in taking over an existing project
1:00:13 - Asses both database and code quality
1:01:08 - Establish and Adhere to professional standards throughout
1:01:30 - Communicate with the client's representatives
1:01:48 - Example of an Initial Project assessment, Yes or No?
1:03:40 - Know your self and your clients
1:04:10 - Managing customer expectations during deployment
1:04:27 - Address any problem squarely and quickly; What you will do to correct the problem and how long will it take
1:06:40 -Do mission critical testing before deploying new programs or updating programs
1:08:47 - Take responsibility for the project
They explain principled approaches to avoiding, identifying , and resolving problems. Numerous examples of real-world incidents are scattered throughout the presentation.
Links in the video:
DISCORD SERVER & Invitation to Join
Discord: discord
Discord: discord
Article ODBC (URL is Case Sensitive)
https://www.accessmvp.com/TomVanStiph...
Table of Contents:
00:06 - Intro Tom van Stiphout and Kim Young
00:25 - Access News and announcements
00:38 - Visit the Access Roadmap for new features
01:24 - Join the Access Discord Server and hang out with other Access developers
03:08 - New and revitalized AUG chapters
07:28 - Begin the presentation
07:40 - We're in Trouble (music)
08:58 - Different Kinds of Error Messages, what do they look like and why
09:10 - 1. An unhandled Accdb error
09:12 - 2. A basic MsgBox for errors
09:22 - 3. A rich, informative custom error message
09:40 - 4. An Unhandled error from an accde
09:55 - 5. Third-Party Error Handler -- VB Watchdog
10:53 - Check the Windows Event Error log with deep technical detail
11:32 - Link to article "Handling ODBC Errors" - Tom van Stiphout
14:15 - Be aware that environmental changes can cause failure, e.g. network interruptions
14:58 - Be aware of potential MS Update and Bug Releases
15:10 - When posting bugs to online forums, the details are important
18:02 - If it's an update bug, try 1st to roll back MS update to last working version
19:09 - Planning and Rehearsal of your recovery plan are essential to prepeare for emergencies
21:04 - Defense Steps at Runtime, when a failure occurs
21:09 - Make backups and store them safely
21:50 - Can you replace a bad FE and trouble-shoot the problem later?
22:44 - Use Task Manager to isolate hidden instances of programs that may be running
23:09 - There is minimal debugging available in accdes
23:30 - Is the error reproducible? Has it been reported online by others?
23:51 - Demo of standard tools using Northwind Dev to show techniques
24:36 - Using the Watch Window in VBE
25:46 - Reviewing the Call Stack for complex processes
27:00 - Debugging in accde is possible in the Immediate Window with proper advance preparation
27:56 - Identify Current Screen and active control and active control values
28:08 - Inspect the state of a running form
28:30 - Pre-placed debugging tools for more extensive review of code
31:06 - Inspect ASCII strings in immediate window
32:20 - DumpRecordset to inspect records
35:44 - Design Time Considerations
36:11 - Defensive programming that anticipates as many possible problems as possible
36:52 - Choose the apropiarte Update Chanel for production applications--Not Current Channel
37:35 - Balance your tolerance of risk with availability of new or improved features in an update
37:52 - Have a "Scout" working on a proof of concept computer on the Monthly Channel to prepare for upcoming changes
38:22 - Implement and use consistent error handling
40:03 - Plan what to track and log to improve user feedback
40:43 - Error logs are a source of valuable information on crashes
41:28 - Design and describe a deployment procedure and execute it!
42:06 - Validate deployment in progress, before and during, don't wait until after
42:56 - Development Discipline produces reliable results
43:13 - App tables to document the current database structure
45:23 - Third-party tools are also available
48:25 - Set aside time to improve your knowledge
52:49 - Consolidate code to improve reliability and maintainability
52:57 - 3 Tier app design,
Data
Logic
Interface
53:15 - Common code belongs in a stand alone module, not repeated in forms
53:51 - Debug.Assert to identify 'unknown else" code at design tme
54:19 - Design time tool rather than runtime error handler
55:36 - Deug.Assert to test incoming parameters, avoiding data and datatype errors
56:39 - Doing nothing has a cost
57:58 - Keep track of known MSFT Bugs like DatePart()
58:44 - Use helper tables, such as a table of dates for example
59:44 - Steps in taking over an existing project
1:00:13 - Asses both database and code quality
1:01:08 - Establish and Adhere to professional standards throughout
1:01:30 - Communicate with the client's representatives
1:01:48 - Example of an Initial Project assessment, Yes or No?
1:03:40 - Know your self and your clients
1:04:10 - Managing customer expectations during deployment
1:04:27 - Address any problem squarely and quickly; What you will do to correct the problem and how long will it take
1:06:40 -Do mission critical testing before deploying new programs or updating programs
1:08:47 - Take responsibility for the project
2 ماه پیش
در تاریخ 1403/02/18 منتشر شده
است.
315
بـار بازدید شده