Created attachment 63972 [details] all necessary files, with examples Problem description: Push buttons have property "Graphics", where you can link (or embed) a graphic file to be displayed on the button. Embedding does not work. Steps to reproduce: 1. Create a new .odb. 2. Create a new form, with one push button. 3. Edit properties of the button, and select [...] button next to the graphics section (see attachment: button_properties.png) 4. Select file with graphics, and UNCHECK 'link' checkbox (see attachment: trying_to_embed_a_picture.png) 5. Click Open. An image is being displayed. 6. Save form, save .dob, and quit Base. Current behavior: When opening saved .odb file, there is no embedded graphics. Expected behavior: The embedded graphics is being added to the .odb file. CUSTOM HACK: I had another .dob file with images, and I browsed .dob in Total Commander, (it seems like a regular .zip file) I was able to manually add an 'embedded' graphic file, by going to: TEST_hacked.odb\forms\Obj12\ and then adding manually a subfolder: TEST_hacked.odb\forms\Obj12\Pictures\ and pasting (from another .odb file) the file: 100002000000006700000029039C94D1.gif NOTE: This .gif has changed name (I do not know what mechanism is responsible for it). The folder 'Pictures' was somehow present in my another .odb file, but not in this sample. So here are attachments: TEST.odb - genuine .dob, with linked image. TTTC.gif - the file to be linked TEST_embedding.odb - this is a result when you try to embed a graphic - it is not being embedded. TEST_hacked.odb - this is file manually modified: - added subfolder "Pictures" - added file 100002000000006700000029039C94D1.gif - modified TEST_hacked.odb\forms\Obj12\content.xml file, so it contains the key: form:image-data="Pictures/100002000000006700000029039C94D1.gif" Please compare this content.xml file with TEST.odb Platform (if different from the browser): Windows 7 64bit Kind Regards, Mateusz
I see the same error with an image button too. I have used LO3.7 (dev) on WinXP.
*** This bug has been marked as a duplicate of bug 47832 ***