[Libreoffice-bugs] [Bug 91828] BASIC - CurrentValues are empty after opening a form which triggers a macro - incorrect event execution sequence onLoad should not occur after onRecordChange

2021-04-18 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=91828

--- Comment #28 from christian_k...@gmx.net ---
Created attachment 171272
  --> https://bugs.documentfoundation.org/attachment.cgi?id=171272=edit
corrected example

example with changed event trigger

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 91828] BASIC - CurrentValues are empty after opening a form which triggers a macro - incorrect event execution sequence onLoad should not occur after onRecordChange

2021-04-18 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=91828

christian_k...@gmx.net changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |WORKSFORME

--- Comment #27 from christian_k...@gmx.net ---
Hi,

I have download the first example and I have got the same behaviour in LO
7.0.4.2 as well as in LO 3.5.4.2. Now I have changed the event trigger of the
form to 'Vor der Datensatzaktion' / before record action, and now it works for
me.

Best regards,
Christian

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 91828] BASIC - CurrentValues are empty after opening a form which triggers a macro - incorrect event execution sequence onLoad should not occur after onRecordChange

2021-04-17 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=91828

--- Comment #26 from QA Administrators  ---
Dear christian_kuhn,

To make sure we're focusing on the bugs that affect our users today,
LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed
bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this
bug report. During that time, it's possible that the bug has been fixed, or the
details of the problem have changed. We'd really appreciate your help in
getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice
from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information
from Help - About LibreOffice.

If the bug is NOT present, please set the bug's Status field to
RESOLVED-WORKSFORME and leave a comment that includes the information from Help
- About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular
meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a
REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your
bug pertains to a feature added after 3.3) from
https://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat:
https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 91828] BASIC - CurrentValues are empty after opening a form which triggers a macro - incorrect event execution sequence onLoad should not occur after onRecordChange

2019-04-18 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=91828

Roman Kuznetsov <79045_79...@mail.ru> changed:

   What|Removed |Added

 Blocks||107659


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=107659
[Bug 107659] [META] Macro bugs and enhancements
-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

[Libreoffice-bugs] [Bug 91828] BASIC - CurrentValues are empty after opening a form which triggers a macro - incorrect event execution sequence onLoad should not occur after onRecordChange

2018-09-14 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=91828

--- Comment #25 from christian_k...@gmx.net ---
Reproduced with:

Version: 6.1.1.2 (x64)
Build-ID: 5d19a1bfa650b796764388cd8b33a5af1f5baa1b
CPU-Threads: 1; BS: Windows 6.1; UI-Render: Standard; 
Gebietsschema: de-DE (de_DE); Calc: group threaded

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 91828] BASIC - CurrentValues are empty after opening a form which triggers a macro - incorrect event execution sequence onLoad should not occur after onRecordChange

2018-09-14 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=91828

--- Comment #24 from christian_k...@gmx.net ---
Reproduced with:

Version: 6.1.1.2 (x64)
Build-ID: 5d19a1bfa650b796764388cd8b33a5af1f5baa1b
CPU-Threads: 1; BS: Windows 6.1; UI-Render: Standard; 
Gebietsschema: de-DE (de_DE); Calc: group threaded

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 91828] BASIC - CurrentValues are empty after opening a form which triggers a macro - incorrect event execution sequence onLoad should not occur after onRecordChange

2018-08-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=91828

--- Comment #23 from QA Administrators  ---
** Please read this message in its entirety before responding **

To make sure we're focusing on the bugs that affect our users today,
LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed
bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this
bug report. During that time, it's possible that the bug has been fixed, or the
details of the problem have changed. We'd really appreciate your help in
getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice
from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information
from Help - About LibreOffice.

If the bug is NOT present, please set the bug's Status field to
RESOLVED-WORKSFORME and leave a comment that includes the information from Help
- About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular
meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a
REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your
bug pertains to a feature added after 3.3) from
http://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat:
https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 91828] BASIC - CurrentValues are empty after opening a form which triggers a macro - incorrect event execution sequence onLoad should not occur after onRecordChange

2017-08-28 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=91828

Alex Thurgood  changed:

   What|Removed |Added

   See Also||https://bugs.documentfounda
   ||tion.org/show_bug.cgi?id=11
   ||2059

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 91828] BASIC - CurrentValues are empty after opening a form which triggers a macro - incorrect event execution sequence onLoad should not occur after onRecordChange

2016-10-06 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=91828

Buovjaga  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEW
 Ever confirmed|0   |1

--- Comment #22 from Buovjaga  ---
Status should be NEW.

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 91828] BASIC - CurrentValues are empty after opening a form which triggers a macro - incorrect event execution sequence onLoad should not occur after onRecordChange

2016-06-14 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=91828

Alex Thurgood  changed:

   What|Removed |Added

Summary|BASIC - CurrentValues are   |BASIC - CurrentValues are
   |empty after opening a form  |empty after opening a form
   |which triggers a macro  |which triggers a macro -
   ||incorrect event execution
   ||sequence onLoad should not
   ||occur after onRecordChange

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 91828] BASIC - CurrentValues are empty after opening a form which triggers a macro

2015-06-23 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=91828

--- Comment #21 from vlad vladboscane...@gmail.com ---
Hi to all.
Well,I am not a developer ,but...
-
The error you have I think is an error in Java,and Java is used only in
HSQLDB,which one are written in above mentioned language.
Then ,the error is :NumberFormatException.
If you will take a look to official Java definitions,
'
http://docs.oracle.com/javase/7/docs/api/java/lang/NumberFormatException.html
'
you can find the definition of this error: the application has attempted to
convert a string to one of the numeric types, but that the string does not have
the appropriate format.
What I am trying to say:this is the bug of enabled database,but not a
LibreOffice,Libre just gives a SQL command to database engine and attend the
anwer.It is possible to write to authors of mentioned database,but I am afraid
that the answer will be:It's time to change version(because the LO version
database is about 10 years old,there are more recent versions.)
Hope it helps.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 91828] BASIC - CurrentValues are empty after opening a form which triggers a macro

2015-06-11 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=91828

Michael Stahl mst...@redhat.com changed:

   What|Removed |Added

 Attachment #116451|application/octet-stream|application/vnd.oasis.opend
  mime type||ocument.database

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 91828] BASIC - CurrentValues are empty after opening a form which triggers a macro

2015-06-10 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=91828

--- Comment #20 from christian_k...@gmx.net ---
Created attachment 116451
  -- https://bugs.documentfoundation.org/attachment.cgi?id=116451action=edit
order of events

(In reply to Lionel Elie Mamane from comment #18)

Something is wrong with the order of the occuring events. The event 'when
loading' should not occur after the event 'before changing record'. The
workaround in your code for this is 

   if IsEmpty(TermID) OR IsEmpty(CtxtID) Then
 exit sub
   end if

I have attached an example to show this.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 91828] BASIC - CurrentValues are empty after opening a form which triggers a macro

2015-06-06 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=91828

--- Comment #18 from Lionel Elie Mamane lio...@mamane.lu ---
Christian, I don't understand. You say that in LibreOffice 4.0.6.2, you got an
empty string instead of a Variant/Empty in the variables IDString, TermID and
 CtxtID, and you say that then the Statement.ExecuteQuery(Sql) does not make
an error.

However, if these variables contain an empty string or they are Empty, the
resulting content of variable Sql is the same, so I don't see how it can make a
difference for your macro.

Anyway, if you want a string, you can easily force that by adding:

  Dim IDString  As String
  Dim TermIDAs String
  Dim CtxtIDAs String


While I read your macro, I notice that in the SQL command (query), you try to
compare an integer column to a string literal. This is not guaranteed to work
on all database management systems. For example, it does not on PostgreSQL:

  ERROR:  operator does not exist: integer = character
  HINT:  No operator matches the given name and argument type(s). You might
need to add explicit type casts.

It happens to work with HSQLDB (or MySQL/MariaDB) because those will do
automatic type conversions.

I suggest that you use integers when comparing to integer. For example
  SELECT Table_2.Nr. FROM Table_2
  WHERE Table_2.Begriff: Nr. = 0 AND Table_2.Kontext: Nr. = 2
instead of
  SELECT Table_2.Nr. FROM Table_2
  WHERE Table_2.Begriff: Nr. = '0' AND Table_2.Kontext: Nr. = '2'

This will be more portable.

In order to avoid trying to use invalid values you could do something like:

1) Leave variables IDString, TermID and CtxtID as Variant.

2) add:

  if IsEmpty(IDString) OR IsEmpty(TermID) OR IsEmpty(CtxtID) Then
exit sub
  end if

before computing the value of sql.


And actually, the most robust way to do that kind of things is not to construct
SQL commands on the fly, but to use parametrised queries:

Option Explicit

Global statement as Object

Sub make_query
  'Exit Sub
  statement =
ThisComponent.DrawPage.Forms.GetByName(frm_tbl2).activeConnection.prepareStatement(SELECT
Table_2.Nr. FROM Table_2 WHERE Table_2.Begriff: Nr. = ? AND
Table_2.Kontext: Nr. = ?)
End sub


Sub Check_rl_term_context
  Dim MainForm  As Object
  Dim ResultAs Object
  Dim Term  As Object
  Dim IDControl As Object
  Dim Context   As Object
  Dim Found As Boolean
  Dim IDValue   As Variant
  Dim TermIDAs Variant
  Dim CtxtIDAs Variant
  Found   = False
  MainForm= ThisComponent.DrawPage.Forms.GetByName(frm_tbl2)
  IDControl   = MainForm.GetByName(Nr-Feld)
  Term= MainForm.GetByName(Begriff-Feld)
  Context = MainForm.GetByName(Kontext-Feld)
  TermID  = Term.CurrentValue
  CtxtID  = Context.CurrentValue
  if IsEmpty(TermID) OR IsEmpty(CtxtID) Then
exit sub
  end if
  statement.setLong(1, termID)
  statement.setLong(2, CtxtID)

  Result = statement.ExecuteQuery()
  While (Not Found AND Result.Next)
If (StrComp(Result.GetString(1), IDValue)  0) Then
  MsgBox(Der Begriff wurde in diesen Kontext schon eingetragen.)
  Term.Reset()
  Context.Reset()
  Found = True
End If
  Wend
End Sub

Where make_query is bound to the form's when loading event.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 91828] BASIC - CurrentValues are empty after opening a form which triggers a macro

2015-06-06 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=91828

--- Comment #19 from christian_k...@gmx.net ---
What I mean is: either the elements of the form should be correctly initialized
before the macro will be executed by the trigger for the event 'before changing
record' (I have not yet noticed for LO 4.0, that the contents of the form's
elements are still empty, if the macro will be executed at first time), or the
macro should not be executed by this event trigger after opening the form,
because for this case the event trigger 'while loading' already exists and such
events are handled by it.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 91828] BASIC - CurrentValues are empty after opening a form which triggers a macro

2015-06-05 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=91828

--- Comment #13 from rob...@familiegrosskopf.de ---
An event could be started by different implementations. There are two
implementations which would happen when changing from one row to another:
com.sun.star.comp.forms.ODatabaseForm
org.openoffice.comp.svx.FormController

The implementation, which fires while opening the form, is ...ODatabaseForm.
Loading of the content is changing the content for this implementation.

You could start your macro like this:
Sub Check_rl_term_context(oEvent AS OBJECT)
IF oEvent.source.ImplementationName = org.openoffice.comp.svx.FormController
THEN

END IF
END SUB

So only one implementation starts - the implementation, which doesn't start
while opening the form.

You are German. Have a look to the Base-Handbuch. It is described at page 412
(Handbuch 4.4). Also the different behavior of ListBoxes is described: page
388.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 91828] BASIC - CurrentValues are empty after opening a form which triggers a macro

2015-06-05 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=91828

--- Comment #14 from christian_k...@gmx.net ---
Not the triggers for the ListBoxes are the problem, but only the form's trigger
which shall trigger the macro before the record will be changed. I mean two
things:

I have seen, that the macro fires two times, one event source is
'com.sun.star.comp.forms.ODatabaseForm' and another is
'org.openoffice.comp.svx.FormController'. And it is described in the
Base-Handbuch for LO 4.4 (p. 141 - 142), that already the opening of the form
is such a changing-the-record-event (ok, I think, I must accept this). But it
is not so easy to understand, why the macro should fire, if the mouse pointer
hovers over the change button after the record was changed, because the
semantics of this event mean 'before changing record'.

If I use the event 'while loading' to trigger the macro, then the ListBoxes are
correctly initialized and have content (CurrentValues are not empty), so that
the SQL query of the example does not fail. But if I use the event 'before
changing record' as trigger, it seems, that the ListBoxes are not yet
initialized and the CurrentValue attributes are still empty, if the macro fires
at first time. In the earlier version of Base (LO 4.0) this causes not an
error, because the CurrentValue attribute of the ListBox contains only an empty
string. Now (LO 4.4) it should contain a number, but it is empty and contains
nothing. 

I have used the If-then-contruct to filter the right event source and it works,
but in my opinion this is a workaround, because the semantics of this event
trigger are not clear for me.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 91828] BASIC - CurrentValues are empty after opening a form which triggers a macro

2015-06-05 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=91828

--- Comment #17 from christian_k...@gmx.net ---
I have opened bug 91879.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 91828] BASIC - CurrentValues are empty after opening a form which triggers a macro

2015-06-05 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=91828

--- Comment #16 from rob...@familiegrosskopf.de ---
This bug description is about three different behaviors in the form:
- changed current value of listboxes
- different implementations for an event
- occuring of an event while moving with the mousepointer over a field in the
navigationbar

One bug - one buggy behavior.

Please open a new bug-description for the mousepointer over the fields and add
an example without all other buggy behavior.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 91828] BASIC - CurrentValues are empty after opening a form which triggers a macro

2015-06-05 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=91828

--- Comment #15 from Alex Thurgood ipla...@yahoo.co.uk ---
So, the question remains ? 
Bug or design feature ?
Or RFE ?

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 91828] BASIC - CurrentValues are empty after opening a form which triggers a macro

2015-06-04 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=91828

--- Comment #12 from christian_k...@gmx.net ---
I have used Windows 8.1.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 91828] BASIC - CurrentValues are empty after opening a form which triggers a macro

2015-06-04 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=91828

Alex Thurgood ipla...@yahoo.co.uk changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEW
 Ever confirmed|0   |1

--- Comment #3 from Alex Thurgood ipla...@yahoo.co.uk ---
Confirming on OSX 10.10.3

Version: 5.1.0.0.alpha1+
Build ID: 55431a84c264a8bcca593b9207aae0ad81d10f30
Locale : fr-FR (fr.UTF-8)

After the MsgBpx, the IDE opens and I get a Basic error :

Erreur d'exécution BASIC.
Une exception s'est produite : 
Type: com.sun.star.sdbc.SQLException
Message: Wrong data type: java.lang.NumberFormatException: For input string:
.

from the follwowing line of code :

Result = Statement.ExecuteQuery(Sql)

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 91828] BASIC - CurrentValues are empty after opening a form which triggers a macro

2015-06-04 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=91828

Alex Thurgood ipla...@yahoo.co.uk changed:

   What|Removed |Added

Version|4.4.3.2 rc  |4.1.4.2 release
 OS|Windows (All)   |All

--- Comment #4 from Alex Thurgood ipla...@yahoo.co.uk ---
I get the same error with 

Version: 4.1.4.2
Build ID: 0a0440ccc0227ad9829de5f46be37cfb6edcf72

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 91828] BASIC - CurrentValues are empty after opening a form which triggers a macro

2015-06-04 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=91828

Alex Thurgood ipla...@yahoo.co.uk changed:

   What|Removed |Added

Version|4.0.3.3 release |4.0.0.3 release

--- Comment #7 from Alex Thurgood ipla...@yahoo.co.uk ---
Also fails on

Version 4.0.0.3 (Build ID: 53fd80e80f44edd735c18dbc5b6cde811e0a15c)
TinderBox: MacOSX TDF Release, Branch:libreoffice-4-0, Time:
2013-01-31_11:01:36

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 91828] BASIC - CurrentValues are empty after opening a form which triggers a macro

2015-06-04 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=91828

christian_k...@gmx.net changed:

   What|Removed |Added

 Status|NEEDINFO|UNCONFIRMED
 Ever confirmed|1   |0

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 91828] BASIC - CurrentValues are empty after opening a form which triggers a macro

2015-06-04 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=91828

--- Comment #11 from christian_k...@gmx.net ---
Created attachment 116290
  -- https://bugs.documentfoundation.org/attachment.cgi?id=116290action=edit
macro for LO 4.0.6

Sorry - I have not reported:

before I changed to LO 4.3 and the to LO 4.4.3, I have used LO 4.0.6.2 
(Build ID: 2e2573268451a50806fcd60ae2d9fe01dd0ce24). 

For this version, I have used a macro like in the attached text snippet, and
here I get no error, if I open the form, because here I get empty strings and
not missing numbers for the CurrentValue attribute of ListBoxes, so that no
error occurs (probably this is wrong).

But in LO 4.0.6, the behaviour of the trigger is the same, if I uncomment the
MsgBox(Test) like in the attached example, it popped up, if I open the form
or if I hover again over the next-record-button with my mouse after I have
changed the record. This implies, that the macro fires in these cases. 

But I think, this should not happen, because the macro should only fire, before
the record is changed (or if the ListBoxes are touched, because I have triggers
here) and not after the form is opened.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 91828] BASIC - CurrentValues are empty after opening a form which triggers a macro

2015-06-04 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=91828

--- Comment #5 from Alex Thurgood ipla...@yahoo.co.uk ---
Same error in 4.0.5.2

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 91828] BASIC - CurrentValues are empty after opening a form which triggers a macro

2015-06-04 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=91828

Alex Thurgood ipla...@yahoo.co.uk changed:

   What|Removed |Added

Version|4.1.4.2 release |4.0.5.2 release

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 91828] BASIC - CurrentValues are empty after opening a form which triggers a macro

2015-06-04 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=91828

Alex Thurgood ipla...@yahoo.co.uk changed:

   What|Removed |Added

Version|4.0.5.2 release |4.0.3.3 release

--- Comment #6 from Alex Thurgood ipla...@yahoo.co.uk ---
This also fails for me on

Version 4.0.3.3 (Build ID: 0eaa50a932c8f2199a615e1eb30f7ac74279539)

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 91828] BASIC - CurrentValues are empty after opening a form which triggers a macro

2015-06-04 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=91828

--- Comment #8 from Alex Thurgood ipla...@yahoo.co.uk ---
Also fails on

Version 3.6.7.2 (Build ID: e183d5b)


@christian : I can not confirm that this is a regression, at the moment, it
looks like this never worked, at least on OSX

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 91828] BASIC - CurrentValues are empty after opening a form which triggers a macro

2015-06-04 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=91828

Alex Thurgood ipla...@yahoo.co.uk changed:

   What|Removed |Added

 Status|NEW |NEEDINFO

--- Comment #9 from Alex Thurgood ipla...@yahoo.co.uk ---
Same error in 

LibreOffice 3.3.0 
OOO330m19 (Build:6)
tag libreoffice-3.3.0.4

so this was a problem from the beginning of the LO project, and probably
inherited from OOo.

@christian : in which earlier versions of LO did it work, and which OS ?

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 91828] BASIC - CurrentValues are empty after opening a form which triggers a macro

2015-06-04 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=91828

--- Comment #10 from rob...@familiegrosskopf.de ---
Since LO 4.1 CurrentValue of a listbox changed to the value, which should be
saved in the database. Older versions will show the text, which could be seen
on the screen.
if you are using macros and do not know which version of LO should be use, you
have to use a function like this:
---
FUNCTION OfficeVersion()
DIM aSettings, aConfigProvider
DIM aParams2(0) AS NEW com.sun.star.beans.PropertyValue
DIM sProvider$, sAccess$
sProvider = com.sun.star.configuration.ConfigurationProvider
sAccess = com.sun.star.configuration.ConfigurationAccess
aConfigProvider = createUnoService(sProvider)
aParams2(0).Name = nodepath
aParams2(0).Value = /org.openoffice.Setup/Product
aSettings = aConfigProvider.createInstanceWithArguments(sAccess, aParams2())
OfficeVersion() = array(aSettings.ooName,aSettings.ooSetupVersionAboutBox)
END FUNCTION
---

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 91828] BASIC - CurrentValues are empty after opening a form which triggers a macro

2015-06-03 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=91828

--- Comment #2 from christian_k...@gmx.net ---
The macro fires, if I hover the next record button with my mouse without to
press it? This is strange ...

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs