The sample files confirmed that it was corruption related, and were enough that I could pinpoint when it happens. Well it turns out to be more common than I thought, as I’ve had a couple of reports already. In BaseElements 3.0.8 I added an error dialog for exactly this and just put a fairly generic “contact support” message in it, as I wasn’t sure at that stage if it was actually corruption related, and also I didn’t think this would occur very often. Count the before and after and you have an error capture where there is none. So when this runs, if there is an issue with one of the files, there will be fewer records in the found set afterwards. Then we have a second import that is using the setting “update matching records in found set”. In the case of BaseElements we start with a list of all of the files in the solution. A import with no error code means you need to know how much data SHOULD have been imported and you can compare it to how much data was imported. An error that gives you some sort of error code is fine, you can at least work around it or allow for it and manage it. ![]() One that seems to come up a lot more often than I’d like are FileMaker files that produce invalid XML, which makes it impossible for BaseElements to import.Įven more frustratingly lately I’ve been seeing bad layout data that doesn’t throw any sort of error, just silently fails on import. ![]() So I see lot of the options and permutations that are possible in various FileMaker files. I spend a lot of my time looking at the FileMaker Database Design Report for BaseElements.
0 Comments
Leave a Reply. |