Open database in local host

[alamsyah78]

I try to open the sample (sample.dna) using DNA 3.0. I follow these steps:

First, I create an SQLite database. No problem was found in this step (see Figure 1) Second, I download the data sample (sample.dna) from Github and save it in the Documents folder. The problem is DNA 3 cannot detect files ( all files and *dna file) in the Documents folder (see Figure 2 and Figure 3)

[leifeld]

See the discussion and solutions in #201. Does this solve your problem?

[alamsyah78]

No. I install Adopt OpenJDK version 11 with Hotspot JVM and give permission to the JAR file in the system setting. But, DNA 3.0 still does not detect my file.

Next, I create a new database (i.e., training.dna) and save it to my hard disk. I closed DNA 3. I open DNA 3.0 again and try to open training.dna file. Unfortunately, I do not find training.dna in my harddisk.

I use macOS Big Sur version 11.6.7.

Regards,

[leifeld]

Does it happen as well if you save the dna file in a Dropbox folder? This is not recommended, but may be useful for testing purposes. If you can then see the file, it means it's a MacOS file system issue. Perhaps you can report back.

[alamsyah78]

Thank you very much for this discussion. I will try DNA 3.0 in Windows in the future. God bless you Prof. Leifeld.

[leifeld]

Have you tried saving the dna file in another folder? Have you tried saving it in a Dropbox folder? It would be good to know these things to understand the nature of the problem better. Thanks.

[maikenmelanie]

Dear Prof. Leifeld, I have the same problem as described in this issue. I was successfully using the DNA 2.0 beta 25 version where I was always able to open the database in the local host. I recently updated my MacBook to the most recent Ventura 13.0 version and since then I am also not able to open the file anymore (undetectable as described in this issue). I tried both: opening it in the Mac file system and in a OneDrive folder, which was unsuccessful. I also checked (as described above) whether the JAR file has all the necessary permissions via the system settings (which it has).

[maikenmelanie]

Small update: Apparently the problem of not being able to see the content of some folders on my Mac does not extend to all folders, if I save the .dna file in the Pictures folder, I am able to open it in the local host.

[leifeld]

@maikenmelanie Thanks, this is a valuable hint about the Pictures folder. I found a similar problem with a different Java application, and it seems to be a problem with the MacOS security settings there.

You wrote that you were using DNA 2.0 beta 25. Can you try downloading the latest version 3.0.8 and try if the problem persists there? You can use the sample.dna database for this purpose or import your 2.0 data into a new database in order to try it out. I'm happy to try to diagnose the problem if it still persists in DNA 3, but I may need your help in trying it out as I don't have a Mac to try it out on with the same issue occurring.

[leifeld]

I have fixed the MacOS problem, and the fix will be released in DNA 3.0.10 in March 2023. For now, there is a temporary version available. The changes in the code can be reviewed here. Let me know if this solves the issues.

[maikenmelanie]

Thank you very much for the update. I am sorry for not getting back to you regarding your question earlier. I tried it with the new temporary version again and the issue seems to still be unresolved. I can open the dna file if it is saved in the Pictures folder, however, I cannot open it when it is saved in other folders (e.g., Documents, One Drive) although I made sure to give the program all necessary permissions.

Am 24.02.2023 um 00:13 schrieb Philip Leifeld @.***>:

I have fixed the MacOS problem, and the fix will be released in DNA 3.0.10 in March 2023. For now, there is a temporary version https://www.dropbox.com/s/k439y68p9znznzr/dna-3.0.10.e1.jar?dl=0 available. The changes in the code can be reviewed here <x-msg://13/60c06615362cf1a552be8c0b314923536d3f9011>. Let me know if this solves the issues.

— Reply to this email directly, view it on GitHub https://github.com/leifeld/dna/issues/244#issuecomment-1442555718, or unsubscribe https://github.com/notifications/unsubscribe-auth/ANZ2AC624HPP25TADSZC7CTWY7VKJANCNFSM52T7YUTQ. You are receiving this because you were mentioned.

[leifeld]

Thanks for getting back to me. Sorry to hear it's still not working. I have only one Mac to try it out with, and it worked there after making the changes. To diagnose the problem better, would you mind opening DNA, going to the message log (click on the little bug in the lower right corner, export the log as a JSON file, and post it here? That should include the operating system type, which is used to decide which file chooser to use. Thanks.

[maikenmelanie]

Yes, sure you can find the JSON file attached, hope it helps. messagelog_dna_maiken.json.zip

[leifeld]

Thanks, much appreciated. I have an idea what may have gone wrong. Would you mind trying it with this new temporary version? Thanks.

[maikenmelanie]

Now I can navigate in my folders to the file location as I have been able to before, this is great. Yet, I get the following message when trying to open the DNA file:

dnalog_maiken.json.zip

[leifeld]

Great! Yes, I noticed in the error log you sent that there was an uncaught error message about not being able to find some of the required tables in the database. My best guess was that you were trying to open a database created in DNA 2.0 with DNA 3.0. This is not possible because the data structures have changed. So I have now added a proper error message when that happens. If you click on the little bug symbol in the lower right corner of the DNA window, you will be able to see the full error message with version numbers and instructions. The good news is that there is an import function that is compatible with version 2 databases. You basically have to create a new database, set up any required coders, and then use the "Import from DNA database" dialog in the "Documents" menu to copy all the documents, statements etc into the new database. This works with database version 2 and 3.

[maikenmelanie]

Thank you very much for checking the error message and for your time and effort in general, this is great.

Am 24.02.2023 um 11:07 schrieb Philip Leifeld @.***>:

Great! Yes, I noticed in the error log you sent that there was an uncaught error message about not being able to find some of the required tables in the database. My best guess was that you were trying to open a database created in DNA 2.0 with DNA 3.0. This is not possible because the data structures have changed. So I have now added a proper error message when that happens. If you click on the little bug symbol in the lower right corner of the DNA window, you can will be able to see the full error message with version numbers and instructions. The good news is that there is an import function that is compatible with version 2 databases. You basically have to create a new database, set up any required coders, and then use the "Import from DNA database" dialog in the "Documents" menu to copy all the documents, statements etc into the new database. This works with database version 2 and 3.

— Reply to this email directly, view it on GitHub https://github.com/leifeld/dna/issues/244#issuecomment-1443397367, or unsubscribe https://github.com/notifications/unsubscribe-auth/ANZ2AC7ANLUPSYJL4R6BWWLWZCB6FANCNFSM52T7YUTQ. You are receiving this because you were mentioned.

[leifeld]

Happy to help. I'll close this as fixed.