Re: [dabo-users] Y2K issue with date fields and multi line text fields

Regarding the date field,

I have attached 4 screen shots. They show before and after an update of birth_date. The interesting thing

is that if you change a date after 1970, it defaults to the 1900s. If birth_date is changed before 1970,

it defaults to the 2000s.

As you can see from the screen shot, Dabo is only seeking a two digit date.

Thanks for all your help!

On Tue 19/06/12 9:47 PM , Ed Leafe ed@leafe.com sent:

> On Jun 19, 2012, at 11:24 AM, Dave Kelly wrote:

> > The Problem is, the date field only accepts two

> digit dates. When I put in> birth dates, they default to the 2000's.

> Therefore, my birthdate in the> database becomes 2064 rather than 1964. How do I

> fix this?

> I'm not sure I understand - what do you mean by "the date field only

> accepts two digit dates"? A dDateTextBox should default to 4-digit

> years.

> > I have an address field which is a varchar(255).

> I exported this from a> Microsoft Access database to Postgres and it has

> multiple lines separated by> crlf. It displays fine in PgAdmin III on Linux

> Mint but in a Dabo text> field it is all on one line with an unprintable

> character between what> should be the lines. How can I make this display

> properly?

> Hmmm... looks like something strange is going on. I just took a dEditBox,

> and set its Value to:r"\n".join(['foo', 'bar', 'baz'])

> I would expect this to show the three words all on separate lines, but

> instead it's showing "foo\nbar\nbaz". I'll have to dig into the code to see

> where it is escaping the newline character.

> -- Ed Leafe

> _______________________________________________

> Post Messages to: Dabo-use

468B-8EC8-C9ADD96A849C@leafe.com

--- StripMime Report -- processed MIME parts ---

multipart/mixed

text/plain (text body -- kept)

image/png

---

_______________________________________________

Post Messages to: Dabo-users@leafe.com