Le 06/03/11 03:16, Christopher S. Knepper a écrit :

Hi Chris,



> 3) Office (Base) crashes when trying to anchor a form field to a frame, 
> entering
> an infinite loop of recovery, crash, recovery, crash. The only way to break 
> out
> of the loop is to cancel the recovery process. This wasn't a huge problem for
> me, because I didn't have any text in the frame, so anchoring to the paragraph
> was functionally equivalent to anchoring to the frame, but it would be a 
> problem
> if I had text in the frame. Also, it's sloppy. Priority: 7 of 10. 
> Incidentally,
> this works in OpenOffice 3.2.1.

https://bugs.freedesktop.org/show_bug.cgi?id=33850
http://openoffice.org/bugzilla/show_bug.cgi?id=115557


> 
> 4) Office (Base) occasionally "forgets" field formatting in tables. I applied 
> a
> DD/MM/YYYY format to a date field and was later surprised to find Office had
> reset that field back to the default of DD/MM/YY. It's an intermittent 
> problem,
> and I haven't yet found any rhyme or reason to what triggers it. Office also
> dropped some of my user-defined formats (phone number - adding parentheses and
> hyphen - and zip code - accounting for zip+4 and adding the hyphen), forcing 
> me
> to re-create those formats... several times. Priority: 6 of 10. It SEEMS to
> remember formatting applied to forms, but I'd rather apply to tables for
> consistency across forms, reports, etc.

Have noticed the date format problem too (2 days ago when trying to
manipulate datetime data). However, date formatting is also reported as
being screwed in Calc, so maybe a larger problem than just with Base.


> 
> 5) Office (Base) won't save some default field values in tables. If you "Save
> as..." it drops both the default value and all fields after the field with the
> default value assigned. See this bug report:
> http://permalink.gmane.org/gmane.comp.documentfoundation.libreoffice.user/3347
> for details. Priority 10 of 10. Without the ability to include default values 
> in
> foreign key fields, Base is, for all practical purposes, unusable. This MUST 
> be
> fixed in order for LO/OO to be a viable product. Incidentally, this works in
> OpenOffice 3.2.1.


Haven't tried this yet, but will try and reproduce. Have you opened a
bug issue for it ?


> 
> It is my hope that others will add to this list (though not TOO many items!) 
> and
> the appropriate developers will fix the problems in this list. LO/OO is too

https://bugs.freedesktop.org/buglist.cgi?quicksearch=libreoffice+database



Alex


-- 
Unsubscribe instructions: E-mail to [email protected]
List archive: http://listarchives.libreoffice.org/www/users/
*** All posts to this list are publicly archived for eternity ***

Reply via email to