When you import a text file into Access and that text file contains tabs or other special characters, the special characters are converted, and then the special characters appear as boxes. Therefore, when you try to use the imported table, you receive unexpected errors.
For some time I have successfully been using DVD Decrypter and DVD Shrink 3.2 to rip, reauthor and burn DVDs (using Nero).
Today I encountered a consistant error when attempting to open the VIDEO_TS folder from DVD Shrink 3.2 indicating 'DVD Shrink encountered an error and cannot continue. Invalid data in file (i.e.) C:The_Pink_PantherVIDEO_TSVTS_05_1.VOB'
I have the entire six DVD set of the Pink Panther series and ripped the first three disks before attempting to open from Shrink. The problem occurs with all three disks VIDEO_TS folders, however it is not the same VOB causing the error in each reqpective folder.
I attempted coping to hard drive using DVDFab Decrypter, as I have had a few disks where DVD Decrypter did not work and this solved the problem, but that did not help. Next I tried a DVD in my library and it worked fine in Shrink. I had already uninstalled and reinstalled Shrink in hopes that this might correct the problem, but it did not.
Has anybody encountered this? Could you suggest something I might try?
The data read from a file wasn't in the expected format. This error has the following causes and solutions:
- A project file or object library file is either corrupted or in a format that can't be understood.Get a new version of the project file or object library file.
- You may have attempted to load an .exe file into a module.Load the source code instead.
- You may have used the References dialog box and Object Browser to add a reference to a file that isn't a valid object library or contains a Basic project in a format not supported by the host application. For example, on the Windows platform, Microsoft Excel can't understand .bas or .frm files, or Microsoft Project files containing Basic code.Load the questionable file into the application in which it was created, and then save it in a compatible format. For example, object library source code can be processed through MkTypLib; and QuickBasic, and Visual Basic code can be saved in text format, and so on.
For additional information, select the item in question and press F1 (in Windows) or HELP (on the Macintosh).
Support and feedback
![Invalid Invalid](https://support.winshuttle.com/hc/article_attachments/360033687252/mceclip0.png)
Have questions or feedback about Office VBA or this documentation? Please see Office VBA support and feedback for guidance about the ways you can receive support and provide feedback.