Description: I am working on a Base project. I have created a simple database with 4 small tables and forms. I was going to create a few queries using the option...Create Query in Design Mode. As soon as I clicked on the option it opened a the Doument recovery window. I have reinstalled LO, checked my profile and several other settings. No luck. ***NOTE the other 2 options to create queries seem to be OK, that is using the Wizard and SQL Steps to Reproduce: 1.Open LO and Base, and create a new database 2.Select Queries 3.Select Create Query in Design View Actual Results: See attached Expected Results: See Attached Reproducible: Always User Profile Reset: Yes Additional Info: Should have opened the Design Query window
Created attachment 156204 [details] LO error message
@Ron : - which database engine are you using ? - which connector and driver version (if any) ? - it might help if you could provide us with a sample database where the problem occurs (bearing in mind that everything you post here or as an attachment is public)
Created attachment 156280 [details] Tiny Base database for test purposes As requested
[Automated Action] NeedInfo-To-Unconfirmed
@Ron : thanks! 1) Opened Players_Bug01.odb in Version: 6.3.2.2 Build ID: 98b30e735bda24bc04ab42594c85f7fd8be07b9c Threads CPU : 4; OS : Mac OS X 10.15.1; UI Render : par défaut; VCL: osx; Locale : fr-FR (fr_FR.UTF-8); Langue IHM : fr-FR Calc: threaded It is an embedded Firebird database. 2) Clicked on Query button, then Create Query in Design Mode 3) A list of tables is displayed to select and add to the query design. No crash. Works for me. Might this be a Windows specific bug ? If so, can't help here.
no problem in Версия: 6.5.0.0.alpha0+ (x64) ID сборки: 89f0af144c18efafe2573801641689a1432c0cae Потоков ЦП: 4; ОС:Windows 10.0 Build 18362; Отрисовка ИП: по умолчанию; VCL: win; Локаль: ru-RU (ru_RU); Язык интерфейса: ru-RU Calc: threaded
@Ron : I'm guessing that either there is something else happening with your installation, or else this was a bug that has been fixed. You might want to try a current daily release build to see if that has fixed your problem. If not, then there is some other issue of which we are not aware.
(In reply to Alex Thurgood from comment #7) > @Ron : I'm guessing that either there is something else happening with your > installation, or else this was a bug that has been fixed. > You might want to try a current daily release build to see if that has fixed > your problem. > > If not, then there is some other issue of which we are not aware. Thanks Alex...you are correct, there was something going on with Win 10 and Ease of Access. I would not have connected the 2. Turns out I was using Ease of Access->Windows Speech Recognition and this was causing the problem with LO. Your guess is as good as mine as to why. Anyway once I closed Speech Recognition the problem was gone. I have been fixing Windows problems for 40+ years and I'm still amazed at what I find. Have a great day. Case closed...Ron(In reply to Alex Thurgood from comment #7)
So closed as WFM by Comment 8