Received: from maia.hub.org (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id 7EC66632815 for ; Thu, 25 Mar 2010 11:43:15 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 17200-04 for ; Thu, 25 Mar 2010 14:43:04 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.153]) by mail.postgresql.org (Postfix) with ESMTP id D7497632805 for ; Thu, 25 Mar 2010 11:43:04 -0300 (ADT) Received: by fg-out-1718.google.com with SMTP id 19so1998249fgg.1 for ; Thu, 25 Mar 2010 07:43:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:received:message-id:subject:from:to:cc:content-type; bh=9jA9gXFTIzeEOyEb50uR4saBFw+Jte/KwNH4avJelBk=; b=INVifrFthgH6lK+GMRYf6eci7U2nTyCs7CKU38Ii+pQQu39FPKQxHafEMqmafxY+4P zuYXekwSYO0MOf34wAbocxH5SPBONDF9VkJfHh+NwRhHXfb/C/t/Zjd5IsS7e3ZR/T5I xlu5Y4Youp33+531YULQMMfN7BrsgUJJ+Jxvk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=uI0GLsh6hpyRET+ajcHVRlsJuB2MDGXJlaRPZN/IM/EAnnlkDF2pO3aw3tUo1z8dzL /mYyUdL0mA3XnZgUX2kZwAU8wvwUjwrFLxmFgDFPLndLoA47ftz4TySqZHQo4YI8PTOV 3u/qnaVaAdJfEzq6WNqD4apko9HMhump+kKP8= MIME-Version: 1.0 Received: by 10.86.2.16 with HTTP; Thu, 25 Mar 2010 07:43:02 -0700 (PDT) In-Reply-To: <4BAB749E.8060009@joops.com> References: <450FAE7A.9070408@joops.com> <6BCB9D8A16AC4241919521715F4D8BCEA356C6@algol.sollentuna.se> <450FC3E0.2030001@joops.com> <6BCB9D8A16AC4241919521715F4D8BCEA356C7@algol.sollentuna.se> <45A60D3E.1060700@joops.com> <45A61751.6040603@mailnetwork.co.uk> <4BAB20BC.3000908@joops.com> <4BAB54FA.1060806@otg-nc.com> <4BAB749E.8060009@joops.com> Date: Thu, 25 Mar 2010 07:43:02 -0700 Received: by 10.87.62.1 with SMTP id p1mr2059910fgk.42.1269528182507; Thu, 25 Mar 2010 07:43:02 -0700 (PDT) Message-ID: <396486431003250743u76fb2a3fqc3c501597f932f55@mail.gmail.com> Subject: Re: Can not access PostgreSQL 8.8 via ADO From: Richard Broersma To: Josef Springer Cc: Chander Ganesan , pgsql-admin@postgresql.org Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-2.599 tagged_above=-10 required=5 tests=BAYES_00=-2.599 X-Spam-Level: X-Archive-Number: 201003/200 X-Sequence-Number: 33999 On Thu, Mar 25, 2010 at 7:35 AM, Josef Springer wrote: > Thanks for quick answer. Sorry, this was a misstype. We are using 8.4 not > 8.8. > > We are using the OLEDB-Provider for ADO. > On 8.2 the connectionstring works, on 8,4 it does not work. > The database is local and accessed with localhost. > An application, whitch acceses the database via an ODBC-driver works. Only > ADO does not work. (ADO error *80004005.* ) If you notice the oledb driver is still marked beta and is not production ready. It also looks like it was last updated 4 years ago. http://pgfoundry.org/projects/oledb/ You should probably use the odbc driver since it is production ready and actively supported. http://www.postgresql.org/ftp/odbc/versions/msi/ -- Regards, Richard Broersma Jr. Visit the Los Angeles PostgreSQL Users Group (LAPUG) http://pugs.postgresql.org/lapug