The question in the dbox specifically asked whether I wanted to import my database from MM4, it didn't mention settings. ... although the dbox heading may have said something about settings, I am not sure.
The point is that there is no way to import db, but not settings, during your MM5 install proc, so you can't rely upon that fact that the user said Yes to import, meaning that people want the db to be created outside the portable installation.
I think that if the user has requested a "portable" installation, you should import data from the user's custom MM4 database, but comment out the custom location in the ini file that you copy into to MM5/portable ... so that the user does get the portable install that they have requested for ... ie. you should not assume that they want the database in a non-portable location, unless you specifically ask them.
Look at whether MM5 persists the ini file if the user allows MM5 to autostart from the install proc, and accepts importation|upgrade of the MM4 db, and then closes MM5 as soon as it completes, without interacting with the UI. ... That is what i did. ... I am fairly confident that I closed MM5 normally, because at that stage I thought that I had a good db, and just wanted to backup it up.
btw It did put a MM5.db into my custom location, and that db's contents were as expected. .... The problem is that when MM5 was started again it went back to MM.db, and upgraded it.
Oh, that reminds me. ... maybe I did interact with the UI once. I think that I opened File|ManageDb, and clicked the backup icon, so I could check the db location ... I didn't run the backup. And then I closed Mm5
Thanks for response.