Bug 121997 - Error message for linked base subforms: 1>number of parameters which is 0
Summary: Error message for linked base subforms: 1>number of parameters which is 0
Status: RESOLVED DUPLICATE of bug 118112
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Base (show other bugs)
Version:
(earliest affected)
6.3.0.0.alpha0+
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-12-09 19:02 UTC by Koritec GmbH
Modified: 2018-12-10 09:24 UTC (History)
0 users

See Also:
Crash report or crash signature:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Koritec GmbH 2018-12-09 19:02:48 UTC 
Sobald eine Verknüpfung von Unterformularen eingerichtet wird, kommt die Fehlermeldung: Die Dateninhalte konnten nicht geladen werden - Parameter-Index out of range (1>number of parameters which is 0)

Das Problem gab es bei keiner von den alten Versionen (5.xxx)
Getestet wurde auf mehreren Rechnern, mit verschiedenen  JDBL-Treibern, macht keinen Unterschied.

Leider verstehe ich die zuvor diskutierten Lösungsvorschläge nicht.
Comment 1 Julien Nabet 2018-12-10 09:00:17 UTC 
Google translation:
As soon as a link of subforms is set up, the following error message appears: The data contents could not be loaded - Parameter index out of range (1> number of parameters which is 0)

The problem did not exist in any of the old versions (5.xxx)
Tested on multiple machines, with different JDBC drivers, makes no difference.

Unfortunately, I do not understand the previously discussed solutions.
Comment 2 Alex Thurgood 2018-12-10 09:10:39 UTC 
So, not really a bug. Not understanding the solution to a behaviour is not a bug.

*** This bug has been marked as a duplicate of bug 118112 ***
Comment 3 Alex Thurgood 2018-12-10 09:24:26 UTC 
@Koritec: two alternative proposed solutions are:

1) use a macro to change the parameter-name-substitution property in the affected ODB :

https://bugs.documentfoundation.org/show_bug.cgi?id=117053#c15

OR

2) physically alter the content.xml file within the ODB file, following:

https://bugs.documentfoundation.org/show_bug.cgi?id=118112#c24