I don't believe so. It has to conform to what the program will recognize and interact with.Is there a way - if so how could I bring back into SwordSearcher files in my SS user module folder with the *bak extension?
Thanks, Regie
Thanks much. I have been trying to use Forge - thus far I have gotten nowhere.I don't believe so. It has to conform to what the program will recognize and interact with.
I believe the extensions have to be either .ss5cmty (commentary) or .ss5book (book).
If you have a work you want to import, you may want to see how best you can import it via Forge.
Get out of SS. Then move the current module somewhere else temporarily (like the desktop in case you want it back). Then just rename modulename.bak to modulename.ss5book if it was a book. (ss5cmty if it was a commentary).Is there a way - if so how could I bring back into SwordSearcher files in my SS user module folder with the *bak extension?
Thanks, Regie
Thank you.Get out of SS. Then move the current module somewhere else temporarily (like the desktop in case you want it back). Then just rename modulename.bak to modulename.ss5book if it was a book. (ss5cmty if it was a commentary).
I have just retried it again. It shows 071.cmty 5/16/2024 11:04PM bak 567KbThank you.
I really appreciate your help. With some further searching of the internet, I discovered how to change the file name extension. If anyone else here needs help in doing that and I can help, just please let me know and I will try to recall and help them if I can. Again thanks - SwordSearcher is by far my favorite bible software.It's very difficult to guess what is happening based on the information provided (for example, .cmty is not an extension SwordSearcher uses), but a .bak file is created in the same folder as your user module, by SwordSearcher, when it is about to edit the file. If something goes wrong, that file may be left there if SwordSearcher is for some reason unable to recover. You can rename .bak to .ss5cmty but ONLY do that if you KNOW that you are recovering a lost module. Maybe look at the file dates. If that bak file is really old and you have a .ss5cmty file of the same name already, maybe there is nothing you need to do. Also, Forge creates a .bak file before writing new content you are compiling in case you did not intend to overwrite the file that was already there, in which case there is no reason to keep it if you are happy with the module that has the .ss5cmty extension. Hard to say based on the incomplete information I have.