I am using a Mac Roman text file user bible to do translation exercises from Wallace. I regularly update this file and import it again and again into the same User Bible in Acc. This has been working fine. Tonight I tried it and it failed to import but it looked like it had succeeded. But my updates were missing. So after searching for obvious file format violations, I removed the bible from the library and remove the file from the Accordance Shared User Bibles and retried the import. No dice. Nothing imported, though on one or two tests I got a zero length file. And the tab that normally opens on successful import failed to open. After trying things like ripping out all most recent changes and seeing if it would import - it wouldn't - I tried creating a new user bible and importing that file. That worked. I went back to my Wallace file and imported it to a different User Bible name, rather than the default name which derives from the text file name, and lo and behold in it came perfectly. I've tried looking for files of related names but cannot see any where it matters - eg. in the Acc dir. tree.

So what is busted exactly ? Any ideas on what I could check next ? I obviously can use the bible text I have but there must be some piece of meta data somewhere that's clogging up the works. I have no idea what I did to upset it but I clearly have. Any suggestions ? Incidentally it does not appear to be specific to a workspace because using a new workspace and importing to the original name fails just the same way.

So I chased this down and perhaps someone could comment on what I've found. The problem appears to have been an issue with temporary files. I ran dtruss on the acord process while attempting an import of to the failing name, "Wallace Wbk". After comparing that with a dtruss of a successful import to another name I noticed that Acc was creating temporary files under /private/var/folders/sc/r7jzvx_c8xj6gs001s71dfbr0000gn/T/TemporaryItems/. And it appears that each time an import is done a new name is created that is related to the bible name. In my case you see all the variations below. As you can see Mar 8th is the last successful creation of one of these :

There are 37. I assume that I hit some sort of limit on the permutations of the file name and further temp file creation based on this name became impossible. I rebooted my iMac and the files under TemporaryItems were deleted and now the import is working again to this name.

So there appears to be a bug related to the repeated import of a user bible. Of course my analysis could easily be a little broken but I do have a workaround now.