Received: from localhost (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id A044363254B for ; Wed, 21 Jan 2009 20:26:54 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 84432-05 for ; Wed, 21 Jan 2009 20:26:40 -0400 (AST) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from mail-qy0-f17.google.com (mail-qy0-f17.google.com [209.85.221.17]) by mail.postgresql.org (Postfix) with ESMTP id D354B63259C for ; Wed, 21 Jan 2009 20:26:40 -0400 (AST) Received: by qyk10 with SMTP id 10so5975035qyk.19 for ; Wed, 21 Jan 2009 16:26:33 -0800 (PST) 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:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=PMJvOIFIcY4NZHumci8gMufqfHoaSn/OGAUBFXGKgfU=; b=Mk+pUl+000IZAmwkuIntT+SuQTD0G7z7u1AWyLwhP/o18RhhHuVQ1izTWhH9YGMMd7 gnKrZmE0248rv9zVuKDnI0E1/mkPyH9F9EMXkWHFAfVmggshmolCf5/VvUXBPTHzd8ba vCvtlFf1VKXU2Cb9PaIVfx09+5vLYYPROIiGE= 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:content-transfer-encoding; b=ppVQDKnD1m/xqZiLseTyIfdNBiC1DKSr/wNioCW86ICcnwtqVMkcZWdaRbiBGFqAmH SQv7j/ZGpqdNfnEmGMeX9H4a5KaGuOog2J0l1QRrm4xqdwXMWA4ESV//KiJN0MtmsY6t b3Tl6hKcSwgR1DMefK7RPcXGPRkPUmVheeBcc= MIME-Version: 1.0 Received: by 10.215.100.3 with SMTP id c3mr387193qam.339.1232583991036; Wed, 21 Jan 2009 16:26:31 -0800 (PST) In-Reply-To: References: Date: Wed, 21 Jan 2009 16:26:31 -0800 Message-ID: <396486430901211626x368b1852hc4dec2492cd42a8e@mail.gmail.com> Subject: Re: ODBC From: Richard Broersma To: Marc Fromm Cc: "pgsql-admin@postgresql.org" Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=none X-Spam-Level: X-Archive-Number: 200901/109 X-Sequence-Number: 31156 On Wed, Jan 21, 2009 at 3:31 PM, Marc Fromm wrote: > Some of our users use an ODBC connection between MS Access and an Oracle > database to work with the data. > Access however has a 255 field/column limit, which the Oracle Db has now > execeded. I am not sure what kind of data model would require 255 columns, but if there is not in fact de-normalization occurring here and you really do need > 255 columns in your tables there is a way to make this work in access. You can create multiple bound table(sort of like a vertically partitioned view). In each bound table in access only include the primary key and a subset of the columns. Of Course this will probably complicate your application design. I don't believe that you can bind oracle table to postgresql. There is a module dbi-link that is similar to what you want to do. This page might give you some ideas about what is available: http://pgfoundry.org/search/?type_of_search=soft&words=dbi+link -- Regards, Richard Broersma Jr. Visit the Los Angeles PostgreSQL Users Group (LAPUG) http://pugs.postgresql.org/lapug