Created attachment 86036 [details] What show up when I click on an existing database Problem description: Steps to reproduce: 1. ....Double click on database 2. .... 3. .... Current behavior: Database starts to open, shows main page with sections for tables, forms, and reports. At this point it hangs. I must force close Base Expected behavior: Database opens and is usable I have upgraded to Fedora FC19-64 and upgraded LO also. I will be going back to the prior release in order to use the database. I can test any fixes on a different pc I use for testing things. Operating System: Fedora Version: 4.1.1.2 release Last worked in: 4.1.0.4 release
Does the same database work with 4.1.0.4, when you have changed to the prior release? Do you use the packages from Fedora or do you use the packages from LO directly, when you had been changed to 4.1.1.2?
Yes, I have gone back to 4.1.0.4 and the database opens. I used the packages from Fedora to go to 4.1.1.2. Should I try the ones from LO directly? Shouldn't they be the same?
(In reply to comment #2) > Yes, I have gone back to 4.1.0.4 and the database opens. > > I used the packages from Fedora to go to 4.1.1.2. > > Should I try the ones from LO directly? Shouldn't they be the same? There could be some differences. I have installed the packages from OpenSUSE and from LO. With packages from OpenSUSE I can connect to some databases, where the connection with direct-LO-packages doesn't work. On the other hand we had bugs about import of some graphics, which doesn't work in openSUSE and Ubuntu, but does work in direct-LO-packages. Could be the same database could be opened by packages directly from LO. Some questions: 1. Is there any macro executed when starting the database? 2. Is it an internal database (HSQLDB)?
Vince, And if you are not working with an embedded HSQLDB, please tell us what backend you are using. If you attach the .odb file itself, that would be helpful. Be aware, though, that attachments are visible to the whole world. `Terry.
I will try with the packages directly from LO and see what happens. There are no macros opened when the database is open. The only add on is Switchboard that allows me to create a menu structure for some common tasks. The database is an embedded HSQLDB. I have considered and tried using MYSQL but I haven't been able to figure it out. I took time off this summer but I will get back to it later. I stopped because 4.0 seemed to have fixed some problems I was having with corrupted data. The database is around 900 kb. I would upload it if necessary. Let me try the LO packages first. It may take me a day or 2 to get it loaded and tested. Thanks for the quick responses.
(In reply to comment #5) > > There are no macros opened when the database is open. The only add on is > Switchboard that allows me to create a menu structure for some common tasks. Switchboard starts automatically when you open the Base-file? So it could be switchboard hangs - not the database itself. > > The database is around 900 kb. I would upload it if necessary. Don't upload such a database with your personal data. First try to open the database without switchboard. If it hangs in the same way open a copy of the database in 4.1.0.4 and remove all data. Then try again with 4.1.1.2. If this has the same buggy behavior you could add this database without content here as attachment.
Success! I used the download from LO to install 4.1.1.2 and it worked. It looks like there may be something is wrong with the Fedora package. Now that I know the LO version works, I intend to go back and reinstall the Fedora packages on my test machine to see if they still fail. I had to re-register the database before it would be recognized and used. I'm not sure what that is all about. Not a biggie - brought up writer and deleted the entry and registered again. Should I leave this open pending the test with the Fedora package?
(In reply to comment #7) > > Should I leave this open pending the test with the Fedora package? Seems to be a bug of Fedora LO. All bugs, which I had found in OpenSUSE-LO and not in the original LO I have reported to OpenSUSE. Could also be that the bug has gone when the next updates were made by Fedora (LO 4.1.2.rc2 is ready ...). So let us close this bug as worksforme. Feel free to reopen it, if you get the reported behavior in the original packages of LO.
OK - Works for me.