From: | "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk> |
---|---|
To: | "Thomas Sandford" <thomas(at)paradisegreen(dot)co(dot)uk>, <pgadmin-support(at)postgresql(dot)org> |
Subject: | Re: "Multiple-step OLE DB operation generated errors" in pgAdmin II:frmSQLOutput.LoadGrid |
Date: | 2002-06-24 07:36:05 |
Message-ID: | D85C66DA59BA044EB96AB9683819CF6101510C@dogbert.vale-housing.co.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-support |
> -----Original Message-----
> From: Thomas Sandford [mailto:thomas(at)paradisegreen(dot)co(dot)uk]
> Sent: 23 June 2002 10:31
> To: pgadmin-support(at)postgresql(dot)org
> Subject: Re: [pgadmin-support] "Multiple-step OLE DB
> operation generated errors" in pgAdmin II:frmSQLOutput.LoadGrid
>
>
> It's no longer a problem for me (I've simply set the dob in
> the records concerned to NULL - I don't have many staff over
> 2000 years old!!)
:-) glad it's working.
> but I guess you might want to see if the
> error is Microsofts or in PGAdmin (someone might have more
> need to store BC dates than I do).
It's almost certainly Microsoft ADO - it's that that raises the error
you got (pgAdmin certainly doesn't) - I would guess as soon as it trys
to parse the BC date that the ODBC driver has just handed it.
:-(
Regards, Dave.
From | Date | Subject | |
---|---|---|---|
Next Message | acchung | 2002-06-24 15:23:33 | passwords |
Previous Message | Thomas Sandford | 2002-06-23 09:31:22 | Re: "Multiple-step OLE DB operation generated errors" in pgAdmin II:frmSQLOutput.LoadGrid |