En Mon, 09 Apr 2007 11:42:33 -0300, <[EMAIL PROTECTED]> escribió:
> Here's my results:
>
> # bad
>
>
>
> # good
>
> datetime.datetime(2007, 4, 9, 0, 0)
You can convert a DbiDate object into a datetime object using:
dt = datetime.datetime.fromtimestamp(float(dbidate))
Only dates after 1970 are
On Apr 6, 10:15 pm, [EMAIL PROTECTED] wrote:
> On Apr 6, 6:20 pm, "John Machin" <[EMAIL PROTECTED]> wrote:
>
>
>
> > On Apr 7, 6:48 am, [EMAIL PROTECTED] wrote:
>
> > > Hi,
>
> > > I am populating a mySQL database with data from the MS Access
> > > database. I have successfully figured out how to
On Apr 6, 6:20 pm, "John Machin" <[EMAIL PROTECTED]> wrote:
> On Apr 7, 6:48 am, [EMAIL PROTECTED] wrote:
>
> > Hi,
>
> > I am populating a mySQL database with data from the MS Access
> > database. I have successfully figured out how to extract the data from
> > Access, and I can insert the data s
On Apr 7, 6:48 am, [EMAIL PROTECTED] wrote:
> Hi,
>
> I am populating a mySQL database with data from the MS Access
> database. I have successfully figured out how to extract the data from
> Access, and I can insert the data successfully into mySQL with Python.
> My problem is that I keep hitting
On Apr 6, 1:48 pm, [EMAIL PROTECTED] wrote:
(snipped)
> If I look in the MS Access database, I see the timestamp as "5/6/112".
> Obviously some user didn't enter the correct date and the programmer
> before me didn't give Access strict enough rules to block bad dates.
> How do I test for a malfor
Hi,
I am populating a mySQL database with data from the MS Access
database. I have successfully figured out how to extract the data from
Access, and I can insert the data successfully into mySQL with Python.
My problem is that I keep hitting screwy records with what appears to
be a malformed dbiD
