Going forward, the pop-up conversion will become tedious for those not ready to migrate.

Expect it would be set per document and recorded per document to user profile.

Once a decision has been made per document, suppressing the "offer" to migrate with a 'Don't ask again' checkbox is as appropriate as having backed out the automatic migration.

Needed for the duration of the transition off HSQLDB.

Don't know if we should say this is importance "medium" and "enhancement". I con't decide this, but for me it is "high" and "major". The migration will come with the following behavior:
Dialog will appear every time you open a database for internal HSQLDB and switch to the tables.
If pressing "Yes" dataloss in most of the databases will be the "normal" behavior. Forms with subforms won't work (bug117589).
This is totally unusable for normal working with databases. It is only experimental.
Everybody who asks me (as author of the German Base-Handbuch) I have answered: Please don't use LO 6.1 together with internal databases. I couldn't help you to get a working migrated database afterwords.

(In reply to robert from comment #2)

Have reset my user-profile after testing with another PC. The dialog doesn't appear any more with a new user-profile and LO 6.1.0.2 on OpenSUSE 42.3 64bit rpm Linux.

(In reply to robert from comment #3)
> (In reply to robert from comment #2)
> 
> Have reset my user-profile after testing with another PC. The dialog doesn't
> appear any more with a new user-profile and LO 6.1.0.2 on OpenSUSE 42.3
> 64bit rpm Linux.

If you reset the user profile, the option 'Experimental feature' get disabled. You have to enable it again to see the dialog...

*** Bug 121587 has been marked as a duplicate of this bug. ***

sorry, it doesn´t help just to close the bug and explain, it is just a duplicate.

And yes, same problematic, but different aspect:

Description:
using a base hsqldb file as a data source causes a pop-up message "Confirm Migration". 
This may be ok, if a user open a base file first time, but unfortunartly this massage appears every time, when you call a connection via macro.

macro stops at this moment and it is never a good idea, when users will migrate at this time!

Remove this message imitatively! 


Steps to Reproduce:
1. register a base file with hsqldb as darta-source

2. write a macro, with uses data out of the database. therefor connect to database 
   
Function knp_getConnection_BaseDok
  Dim oDBC As Variant
  Dim oDataSource As Variant
On Error Goto Fehler:
  oDBC = createUnoService("com.sun.star.sdb.DatabaseContext")
  oDataSource = oDBC.getByName("NameofDataSource")
  knp_getConnection_BaseDok = oDataSource.getConnection("","")
Fehler:
End Function

3. run macro - 

Actual Results:
popup message appears at every connection call and every data-transfer

Expected Results:
no popup at all!!


Reproducible: Always

And:

This is NOT an enhancement. It is a critical bug!

All programmed macro-applications which uses a datasource based on a HSQLDB Base File is broken!!

Hmm, I am not allowed to change priority.... so someone has do do this with more rights.

Hopeful someone is a practical person and knows how LO is used in productivity outside....

(In reply to Thomas Krumbein from comment #8)
> Hmm, I am not allowed to change priority.... so someone has do do this with
> more rights.
> 
> Hopeful someone is a practical person and knows how LO is used in
> productivity outside....

First there will come a time, when the HSQL support is removed from LO, when this behavior will be appropriate.

For now though with HSQL support still in the package it is not a requirement. 

Offering to do so when an ODB is opened directly from Base IMO is a good nudge.

Offering the option on the prompt dialog to not do so again, I would assume this is a session only choice, keeps it unobtrusive.

Changed importance to high. Given some other open issues at the moment this option to begin the migration assistant from outside of the Base module can leave the user in a precarious situation with this datasource requiring at a minimum they close the LO session completely and relaunch the application to get back the ability to work with the data inside.

(In reply to Drew Jensen from comment #9)
> (In reply to Thomas Krumbein from comment #8)
> > Hmm, I am not allowed to change priority.... so someone has do do this with
> > more rights.
> > 
> > Hopeful someone is a practical person and knows how LO is used in
> > productivity outside....
> 
> First there will come a time, when the HSQL support is removed from LO, when
> this behavior will be appropriate.
> 
> For now though with HSQL support still in the package it is not a
> requirement. 
> 
> Offering to do so when an ODB is opened directly from Base IMO is a good
> nudge.
> 
> Offering the option on the prompt dialog to not do so again, I would assume
> this is a session only choice, keeps it unobtrusive.

I would add this that turning this feature, launching the MA from outside of Base, would be appropriate with the final release of LO which contains HSQL support, so the nudge to convert gets some umph behind it.

For what it's worth, Firebird is nowhere near ready for use by the general public, and I do not believe migration should even be an option (except for beta testers.)  After seeing the pop-up for months, I finally decided to migrate a db.  After all, you wouldn't ask people to migrate to a new db if it wasn't ready would you?

Relational db's are new for me, and I've spent days upon days studying and learning to a point where I could make some simple db's.  That was a lot of work, and I felt good about it. After migrating, however, that db was completely useless.  I couldn't do anything with it, and I do not have the SQL knowledge to debug something like that.

So, I figured that, since I've seen postings saying that HSQL is being deprecated, that I might as well just rebuild the db in Firebird.  I spent a couple days rebuilding it, then I hit some new bug.  I've spent hours upon hours trying to figure out this new problem to no avail.  

While I cannot say that all the problems I had are due to Firebird, I can say this: with HSQL, at least I had a usable, working db that I could focus on adding to and building.  With Firebird, the amount of time I spend dealing with problems is orders of magnitude greater than the amount of time I've spent actually using the db I tried to build, and I don't have anything that works.  It's definitely not ready for regular users and this reflects extremely poorly on the entire LO project.

Changing priority back to 'medium' since the number of duplicates is lower than 5