Re: [libreoffice-users] Re: Base/Firebird Queries broken

2019-01-16 Thread Robert Großkopf
Hi Drew, > > Yes, I have a suggestion - there is a property in the Base file which is > incorrectly set during the Migration Assistant run and must be fixed. The > error message looks like this is what is biting you. > > The fastest way to fix it is at follows: > Close the base file and exit

Re: [libreoffice-users] Re: Base/Firebird Queries broken

2019-01-16 Thread Drew Jensen
Howdy Paul, No you don't need to go back - the parameter substitution is for problems with sub forms and now I think you are just dealing with SQL differences between HSQL and Firebird with regards to how it implements joins in select statements. On Wed, Jan 16, 2019 at 2:36 PM Paul D. Mirowsky

Re: [libreoffice-users] Re: Base/Firebird Queries broken

2019-01-16 Thread Paul D. Mirowsky
Hello Drew I assumed that you are answering the question on error 104. I changed the file as per your instructions to db:parameter-name-substitution="true" , but error 104 is still there. Do I have to go back to my original file a migrate again with this fix or am I fixing SELECT

Re: [libreoffice-users] Re: Base/Firebird Queries broken

2019-01-16 Thread Drew Jensen
Also - if you would prefer you can make this fix with a small basic macro. If you would rather go that way here is what you do. Open the Base file in Libreoffice. From the menu select: Tools -> Macros -> Organize Dialogs. On the Organize Dialogs dialog select the 'Libraries' tab. On this tab

Re: [libreoffice-users] Re: Base/Firebird Queries broken

2019-01-16 Thread Drew Jensen
Howdy, Yes, I have a suggestion - there is a property in the Base file which is incorrectly set during the Migration Assistant run and must be fixed. The error message looks like this is what is biting you. The fastest way to fix it is at follows: Close the base file and exit LibreOffice. Rename

Re: [libreoffice-users] Re: Base/Firebird Queries broken

2019-01-16 Thread Paul D. Mirowsky
Found this at https://stackoverflow.com/questions/31611233/determine-firebird-version-with-sql-version-2-1 |SELECT rdb$get_context('SYSTEM','ENGINE_VERSION')... -- ENGINE_VERSION >= 2.1 Only problem is, when run as "Execute SQL Statement" menu item, it errors as 1: firebird_sdbc error:

Re: [libreoffice-users] Re: Base/Firebird Queries broken

2019-01-16 Thread Robert Großkopf
Hi Paul, I would remove >> >>> "Ions-IM"."Select" = TRUE and >>> "Equipment"."Series" = 134 and try the query again. Both commands are right in the internal Firebird-Database. I could test it with with LO 6.1.4.2 here. But could be there is something wrong with the fields ... Is there

[libreoffice-users] Re: Base/Firebird Queries broken

2019-01-15 Thread Alexander Thurgood
Le 16/01/2019 à 00:19, Paul D. Mirowsky a écrit : > Invalid usage of boolean expression This bug perhaps ? http://tracker.firebirdsql.org/browse/CORE-5367?page=com.atlassian.jira.plugin.ext.subversion%3Asubversion-commits-tabpanel Not sure which version of Firebird we are using in LO - 3.0.1

Re: [libreoffice-users] Re: Base/Firebird Queries broken

2019-01-15 Thread Paul D. Mirowsky
I have replaced blanks with underscores in field names in tables. I have removed alias named fields from queries. It did not appear to make a difference. I should note that tables Amps, Volts-High and  Volts-In have the same or more field names. As each table name is prefixed to a field, I

Re: [libreoffice-users] Re: Base/Firebird Queries broken

2019-01-15 Thread Paul D. Mirowsky
See below... On 1/15/2019 10:37 AM, Robert Großkopf wrote: Hi Paul, Have a look at "Ions-IM"."Select" = TRUE Did the migrationtool set the field "Select" to a BOOLEAN-field? Yes "Equipment"."Series" = 134 Did the migrationtool import the field as a INTEGER field? Not quite. Series is

[libreoffice-users] Re: Base/Firebird Queries broken

2019-01-15 Thread Alexander Thurgood
Le 15/01/2019 à 16:14, Paul D. Mirowsky a écrit : Hi Paul, > SELECT "Equipment"."ID", "Equipment"."P_Model", > "Equipment"."P_Model_No", "Equipment"."Power Meter", Check that the space in the field "Power Meter" isn't causing an issue. There was a known bug about spaces being misinterpreted

Re: [libreoffice-users] Re: Base/Firebird Queries broken

2019-01-15 Thread Robert Großkopf
Hi Paul, Have a look at > "Ions-IM"."Select" = TRUE Did the migrationtool set the field "Select" to a BOOLEAN-field? > "Equipment"."Series" = 134 Did the migrationtool import the field as a INTEGER field? There is no function in the query, only 4 tables connected ... The only possibility to

Re: [libreoffice-users] Re: Base/Firebird Queries broken

2019-01-15 Thread Paul D. Mirowsky
Here is the query... SELECT "Equipment"."ID", "Equipment"."P_Model", "Equipment"."P_Model_No", "Equipment"."Power Meter", "Equipment"."Power_No", "Equipment"."Ion Meter", "Equipment"."Ion_No", "Equipment"."Series", "Equipment"."Power Meter 2", "Equipment"."Power_No 2", "Equipment"."Power

[libreoffice-users] Re: Base/Firebird Queries broken

2019-01-15 Thread Alexander Thurgood
Le 15/01/2019 à 00:23, Paul D. Mirowsky a écrit : > Any hint as to where I'm going wrong. Without the query definition, it is going to be like gazing into a crystal ball...all sorts of things might not work in the same way, the time values, the date values (especially if there are calculations),