--- On Thu, 11/13/08, Derek Atkins <[EMAIL PROTECTED]> wrote:
> From: Derek Atkins <[EMAIL PROTECTED]>
> Subject: Re: String lengths in the SQL backend
> To: [EMAIL PROTECTED]
> Cc: "Gnucash list" <[EMAIL PROTECTED]>, [EMAIL PROTECTED], "Phil Longstaff"
> <[EMAIL PROTECTED]>
> Date: Thursday, November 13, 2008, 8:11 AM
> Paul Schwartz <[EMAIL PROTECTED]> writes:
>
> > I've worked with several accounting packages, and
> I would find it
> > very strange if someone could not adapt their
> procedures to live
> > with 32 for the length of the account code.
>
> Except that the UI makes no limitation on the field size...
> So people who convert over could lose data.
>
> > Please remember to CC this list on all your replies.
> > You can do this by using Reply-To-List or Reply-All.
>
> -derek
>
True. Introduction of this "feature" should come with sufficient warnings so
that the user could adjust his account tree appropriately for this one time
event.
Is anything ever perfect?
Paul
_______________________________________________
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel
