https://bugs.documentfoundation.org/show_bug.cgi?id=146836
--- Comment #6 from Jean-Pierre Ledure <j...@ledure.be> ---
I confirm that when the 3rd form ("F1xEMPRESA") is opened, and when the "Salir"
button is pressed:
- in 7.3 an empty message box appears, what should not happen
Version: 7.3.0.2 / LibreOffice Community
Build ID: f1c9017ac60ecca268da7b1cf147b10e244b9b21
CPU threads: 6; OS: Linux 5.4; UI render: default; VCL: kf5 (cairo+xcb)
Locale: en-US (en_US.UTF-8); UI: en-US
Calc: threaded
- in 7.2 the form is closed normally
Version: 7.2.4.1 / LibreOffice Community
Build ID: 27d75539669ac387bb498e35313b970b7fe9c4f9
CPU threads: 6; OS: Linux 5.4; UI render: default; VCL: kf5 (cairo+xcb)
Locale: fr-BE (en_US.UTF-8); UI: en-US
Calc: threaded
The behaviour observed in 7.3 seems related to a weird behaviour of the Basic
interpreter.
Steps to reproduce:
1. Open the provided FINCAxFIREBIRD_ejemplo.odb file.
2. Edit Macro sub CERRAR() in module F1xEMPRESA in the odb file. Put a
breakpoint on line 4:
MCLOSE(acForm,"F1xEMPRESA")
3. Open form F1xEMPRESA from the usual Base welcome screen, and press the
button "Salir" in the form. Nothing happens because in the background the
execution is suspended on the breakpoint.
4. Go to the Basic IDE. The execution is suspended on line 4.
5. Press F8 to debug step by step. The execution umps to line 104 of the DoCmd
module of the Access2Base library.
6. Watch in the watch window the 3 arguments of the mClose() function:
pvObjectType (2)
pvObjectName ("F1xEMPRESA")
pvSave ("<missing parameter>")
7. Execute 3x Shift+F8 up to but not including line 108.
8. Press F8 to execute line 108
mClose = False
=> Suddenly and unexpectedly all 3 arguments became "<Out of Scope>"
??
Of course, with puzzling arguments, the execution of the Basic code becomes
erratic.
In 7.2 the same scenario does not alter the value of the 3 arguments of the
mClose() function.
Until other evidence I do not consider that the root cause of the bug is to be
found in the Access2Base code.
Of course, I stay open for further discussion.
Anyway I confirm the bug as a confirmed regression.
--
You are receiving this mail because:
You are the assignee for the bug.
