I attempted to upgrade from LibO 4.3.6 to 4.3.7
When starting one of my databases with an opening macro the program crashes without any detailed message... see error message log below. When disabling the macros and launching the form it crashes also when laoding the records in the form.
This is annoying and I had to revert to previous version. This is also occuring with the thread 4.4.x
Error event log :
[ Name] Windows Error Reporting
- EventID 1001
[ Qualifiers] 0
[ SystemTime] 2015-05-10T16:59:18.000000000Z
Created attachment 115501 [details]
Crash report associated with the reported error
Attached is the AppCrash Windows file associated with the event
Could you rename your LO directory profile (see https://wiki.documentfoundation.org/UserProfile#Windows) and give a new try?
I have renamed the directory as suggested. The same behavior occurs with the message "Libre Office a cessé de fonctionner". When disabling the startup macro. The same occurs when loading any form.
Thank you for your feedback.
Would it be possible you attach an example file so we can try to reproduce this?
Created attachment 115511 [details]
Attached is a test file made from my current data base with sanitized data. I have checked that it produces exactly the same effect of crashing when loading a form, either from the startup macro of directly. You'll need to activate macros first. Thanks for your help !
Thank you again for your feedback, I'll give it a try after my day time job.
I can confirm crash with LO 4.4.2, win7
Created attachment 115526 [details]
On pc Debian x86-64 with master sources updated yesterday, I don't reproduce the crash.
However, I noticed some console logs, see attachment.
This bug might be a duplicate of https://bugs.documentfoundation.org/show_bug.cgi?id=90614
I opened the form "Comptes" and had a look at the field "Zone Combinee 1" (listfield upper left ...)
Code: SELECT DISTINCT "Compte" FROM "Comptes" ORDER BY "Compte" ASC
Bounded Field: 1
... but there is no bounded field 1, only a field at position 0.
The crash had been fixed by Lionel for LO 4.4.4.
The crash is the bug, but the code for the listfield is wrong, too.
I can confirm that changing the value of the above mentionned bounded field to 0 solves the issue. Many thanks for identifying this.
(In reply to mrcbsx from comment #10)
> I can confirm that changing the value of the above mentioned bounded field
> to 0 solves the issue. Many thanks for identifying this.
So I will set this bug as duplicate of Bug90614.
*** This bug has been marked as a duplicate of bug 90614 ***