Tim: Thank you for the info about 13.5 vs 13.6.
The app is going to be revved to work with V15/16 in the very near future so i'll hold off on moving the fields outside the data file until after the update. The log files are gone since I've restored the entire VM from a backup. :-( *Gory Details* I'm not sure if this was a 4D issue or a Parallels+Win7 issue. So far, the only damaged structures were two versions of a specific app, each of which I modified by changing the location of BLOB/picture fields, then running Apply to selection, and, when I wasn't seeing the BLOB/picture files in the data file folder, I updated records using a For loop to modify a field value. The modification code was not running in a transaction so that removes the issue mentioned in ACI0086904. It could have been the oopsie that was resolved by ACI0087898 but *slow* write speed is probably not an issue. The dev machine is a 15" MacBook Pro with a 512 GB SSD (>100 GB available in the VM as well as > 100 GB available on OS X) that writes at well over 100 MB/s on Win7 (file size varies the speed, as expected). Also, I didn't open the app to repair it. I launched the structure using 13.5 Server and got the "This application is damaged" alert (not sure if it use the exact words "this application"). HTH someone else who runs into this. -- Douglas von Roeder 949-336-2902 On Tue, Nov 15, 2016 at 11:12 AM, Timothy Penner <[email protected]> wrote: > > Also, both versions of the structure that I modified now opens as > damaged and are not repairable. > > What's the error you get from the MSC? > > Maybe it is related to a bug that is already fixed in the final version of > 13.6... > > ACI0086904 Deleting some records while in a transaction generates orphan > blobs. > Deleting some records while in a transaction generates orphan blobs. > > or > > ACI0087898 Repairing a database with an orphan blob can corrupt the data > In certain circumstances, depending to the size of the record and also the > speed of the write > on disk, when repairing a data with Orphan blob, the data could be > corrupted. > > ^ both of the above bugs are fixed in 13.6: > http://download.4d.com/Documents/Products_Documentation/LastVersions/ > Line_13/VIntl/PDF_Format/Fixed_Bugs/Fixed_Bugs_4D_13.6.pdf > > -Tim > ********************************************************************** > 4D Internet Users Group (4D iNUG) > FAQ: http://lists.4d.com/faqnug.html > Archive: http://lists.4d.com/archives.html > Options: http://lists.4d.com/mailman/options/4d_tech > Unsub: mailto:[email protected] > ********************************************************************** > ********************************************************************** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: http://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
