Don Parris wrote:
Hi Don,
(1) I used the "Open With..." feature in Firefox to open the DB with OOo,
rather than saving the file first. I successfully opened both forms that I
work with.
(2) I used "Save as" to overwrite the local copy with the new, updated copy
of the DB.
(3) I closed/reopened the DB and began having problems using the forms
again.
(4) I used "Save as" again to save the copy with a different file name.
(5) I closed the database and set it up as a new database in the DB options
dialog
(6) I opened the new database and opened both forms, one which gave an
error
message about the PK field.
(7) I closed and reopened the DB and tried again. Success!
(8) I closed and reopened the DB again, for good measure. No crash, no
error messages. Also note that the forms are more responsive than they
have
been on Ubuntu.
I have been having similar issues with saving a copy of a form to an NFS
file share repository, (Save as Copy menu entry), and then opening that
form directly from the file share. If the Base document is open, or even
another Writer document already open, I systematically get screen
corruption of the form controls on the form I have opened from the NFS
file share, whereby all of the controls are shifted to the top left hand
corner.
The only way around this problem is to completely shut down any of the
running office processes and restart the application, which is not a
solution since I actually have two forms that need to be open at the
same time.
This problem occurs with a Mandriva packaged version, the m180 dev
version and also the current Ubuntu packaged version of OOo. It is very
frustrating because if the Writer document that contains the form is
opened in write mode, a normal user habitually answers yes to the
automatically proposed "The contents of this file have changed. Do you
want to save ?", which has the immediate effect of bombing the form and
rendering it unusable.
I shall be filing an issue on this problem, which I have had for some
time (basically since we moved to 2.0 and up), because initially I
thought it was a problem with actual corruption of the file during NFS
write.
The problem has never occurred with 1.1.x versions, but of course, the
Base module didn't exist in the same "shape" in those versions.
Alex
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
