Created attachment 169573 [details] Test document I created a new database that is connected to Microsoft SQL Server Express 2019: JDBC driver class: com.microsoft.sqlserver.jdbc.SQLServerDriver Datasource: sqlserver://127.0.0.1:1433;databaseName=test The database contains the two tables Table_1 and Table_2. Form wizard is used to create a main form of table_1 with a subform of table_2. When the form is opened error "The data could not be loaded." "The index 1 is out of range" appears. The main form appears to work but the subform does not display any data at all.
Created attachment 169574 [details] Form error message
Created attachment 169575 [details] MS SQL test database
Have had a look at this. Inside the *.odb-file is a file "content.xml" Could be seen with a packing program. This file contains db:parameter-name-substitution="false" which shouldn't be "false". Set it to "true". You could do this by opening the database, go to Edit → Database → Advanced settings and choose "Replace named Parameters with '?'" If it is chosen the subforms should work.
Please close this bug as WORKSFORME, if it doesn't exist any more after changing "Replace named Parameters with '?'"
Thank you for looking into this. Is this bug fixed or must the workaround be used for each new document created?
(In reply to micke82 from comment #5) > Thank you for looking into this. Is this bug fixed or must the workaround be > used for each new document created? If you could change the behavior by setting Edit → Database → Advanced settings and choose "Replace named Parameters with '?'" it isn't a bug. You had chosen a JDBC-connection. You have to know if the database, which you try to connect, will allow to replace named parameters by '?'. Seems there are databases, which doesn't allow it. So it is set to 'no' by default. If the problem appears and there is no possibility to change this in the GUI it will be a bug.
Thank you for the clarification. I did the same thing with ODBC and it was working. So I guess this is a property (limitation?) of the driver and not the database.
I will set this one to WORKSFORME, because it could be solved by an entry in GUI.