What steps would you take in diagnosing an application that has been changed from its original state? How does this affect the level of support required to facilitate Microsoft® Access® users?

Diagnosing an application that has been changed from its original state involves several steps. Here's a general approach you can take:

1. Gather information: Begin by collecting as much information as possible about the application. This includes the specific changes made, the symptoms being experienced, and any error messages or unexpected behavior encountered.

2. Reproduce the issue: Try to recreate the problem scenario to ensure it is reproducible. This will help in understanding the exact steps that trigger the issue.

3. Analyze the changes: Review the modifications made to the application. This may involve examining the code, database structure, or any other changes that have been implemented. The goal is to identify any potential causes or areas that might be affecting the application's functionality.

4. Test and debug: Perform testing to isolate the issue and narrow down its source. This may include stepping through the code, checking data integrity, or executing specific scenarios to identify problematic areas.

5. Consult documentation and resources: Refer to any available documentation, such as application manuals, technical guides, or relevant online resources. This can help you understand the intended behavior of the application and identify any common issues or solutions related to the changes made.

6. Seek expertise: If you're unable to resolve the issue on your own, reaching out to a more experienced developer or support professional can be helpful. They might have encountered similar issues before and can provide guidance or assistance in resolving the problem.

Regarding the level of support required to facilitate Microsoft® Access® users, it depends on the complexity of the changes made and the proficiency of the users in Access. If the changes have significantly altered the application or if the users are not familiar with Access, they may require more support. This could involve providing technical guidance, training on the modified features, or even redeveloping parts of the application to ensure it meets their needs.

However, if the changes are minor and the users have a good understanding of Access, the level of support required may be relatively lower. It could be as simple as explaining the changes and providing some documentation or instructions to help them adapt to the modified application.