Learn how to recover your DataSnipper work when data conflicts occur between V5 and V6 versions. This step-by-step guide will help you restore your snips and document references to maintain audit trail integrity.
In this guide, you will learn how to:
- Identify when version compatibility issues have occurred
- Extract and preserve your DataSnipper work using proper recovery techniques
- Convert recovered data to V6 format
- Merge recovered work back into your primary workbook
- Implement prevention strategies to avoid future compatibility issues
Understanding Version Compatibility Issues
DataSnipper V5 and V6 use different data storage structures. When work is performed in V5 on a workbook that has been converted to V6, the different XML schemas can create data conflicts. This may result in a "Remove Data" prompt in V6, which is a protection mechanism to maintain workbook integrity.
Step-by-Step Recovery Process
Step 1: Verify Data Accessibility
Using DataSnipper V5:
- Open the affected workbook in DataSnipper V5
- Confirm that your snips and document references are visible and accessible
- Identify all cells containing the work you need to recover
Step 2: Extract Your DataSnipper Work
Select and copy your data:
- Use Excel's selection tool to select all cells containing your DataSnipper work
- Include all relevant cells with snips, document references, and annotations
- Press
Ctrl + Cto copy the selected data (use keyboard shortcut for optimal results)
Step 3: Transfer to Clean Workbook
Create a recovery workbook:
- Open a new, clean Excel workbook
- Click on cell A1 or your preferred starting position
- Press
Ctrl + Vto paste your copied data (use keyboard shortcut for optimal results) - Save this workbook as your recovery file
Step 4: Convert to V6 Format
Upgrade the recovery workbook:
- Open the recovery workbook using DataSnipper V6
- Allow V6 to convert the workbook to V6 format
- Verify that all snips and document references function correctly
- Save the converted workbook
Step 5: Merge Recovered Data
Integrate with your primary workbook:
- Open your primary workbook (after resolving the initial compatibility issue)
- Copy the recovered data from the converted recovery workbook
- Paste it into the appropriate location in your primary workbook
- Verify that all DataSnipper functionality works correctly
- Save your completed workbook
Important Considerations
Recovery Success Factors
The effectiveness of this recovery process depends on several factors:
- The extent of the version compatibility conflict
- How quickly the recovery process is initiated after the issue occurs
- The complexity of the DataSnipper work being recovered
When to Contact Support
If the recovery process does not restore your work completely, DataSnipper support can provide additional assistance for non-confidential workbooks. Our technical team can analyze specific compatibility issues and may offer advanced recovery options.
Prevention Best Practices
Coordinate version upgrades:
- Ensure all team members upgrade to V6 simultaneously
- Remove V5 installations after successful V6 deployment
- Establish clear communication protocols for version updates
Implement access controls:
- Restrict access to converted workbooks until all users have upgraded
- Maintain backups before performing version conversions
- Conduct regular version audits across your organization
Technical Note
DataSnipper uses keyboard shortcuts (Ctrl + C and Ctrl + V) in this recovery process because they preserve additional metadata that is essential for maintaining DataSnipper functionality. Right-click copy and paste methods may not preserve all necessary data relationships.
Conclusion
This recovery process enables you to restore DataSnipper work affected by version compatibility issues, maintaining your audit trail integrity and minimizing workflow disruption. By implementing the prevention strategies outlined above, you can avoid future compatibility conflicts and ensure smooth version transitions across your organization.
For additional support with complex recovery scenarios, contact our technical support team through your standard support channels.