Re: problem after upgrade --- (U/D)

From: Chris Gamache <cgg007(at)yahoo(dot)com>
To: Jeff Silberberg <jsilberberg(at)mindspring(dot)com>, pgsql-odbc(at)postgresql(dot)org
Subject: Re: problem after upgrade --- (U/D)
Date: 2003-04-03 14:04:10
Message-ID: 20030403140410.75614.qmail@web13808.mail.yahoo.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-odbc


When you say Access reports the tables as public.Table, is that in the "table
view" ?

Do an ODBC trace and see what SQL query it uses to pull the name of the
tables... Conversely, you can enable verbose SQL logging in PostgreSQL and see
it on that end... As a matter of fact, it might be easier to read from the
postgresql end. set debug_print_query = true in
/usr/local/pgsql/data/postgresql.conf, and pg_ctl restart. that may shed some
light on what it is doing.

Did you ask about the "preferred" upgrade path from 6.4 to 7.3?

--- Jeff Silberberg <jsilberberg(at)mindspring(dot)com> wrote:
>
> Using ODBC 7.00.02.05 ---
> Latest at ftp://ftp.us.postgresql.org/odbc/versions/msi/
>
> Entered the SET in the Connect Setting on Page 2.
>
> No Joy, still getting the names of the Tables as public.Table ......
>
> Anyone use have a suggest, or know why this might not be functioning ??
>
>
>
> At 01:05 PM 4/2/2003 +0200, you wrote:
> >Hi,
> >try to add the next sentence to the driver configuration: into the "connect
> >settings"
> >
> >SET search_path = public, pg_catalog;
> >
> >Regards
> >
> >Miguel Juan
> >
> >----- Original Message -----
> >From: "Jeff Silberberg" <jsilberberg(at)mindspring(dot)com>
> >To: <pgsql-odbc(at)postgresql(dot)org>
> >Sent: Tuesday, April 01, 2003 7:44 PM
> >Subject: Re: [ODBC] problem after upgrade ---
> >
> >
> >:
> >: Afternoon all,
> >:
> >: We have been using the PostgreSQL with 6.4 and the WIN ODBC
> >: drivers for a number of years. The ODBC is a link to reporting writting
> >: and mostly enables MS Access & Crystal Reports users access to an
> >: applications database. My problem is that we have literally Hundreds of
> >: queries and reports written and none of them now work. The reason is that
> >: when we did the upgrade to PostgreSQL 7.3 recently and now when we link to
> >: the DB/Tables they all come back as public_nnnnnnnnn and therefore, none
> >: of the existing references work.
> >:
> >: I am sure someone else must have worked through this by now,
> >: although I have only seen limited references to this issue in my searches
> >: which is the reason for my post. I really do not want to rebuild all of
> >: these tools !!
> >:
> >: TIA,
> >: JMS...
> >:
> >: Jeffrey Silberberg
> >: CompuDesigns, Inc.
> >: Atlanta, GA. 30350
> >:
> >:
>
> Jeffrey Silberberg
> CompuDesigns, Inc.
> Atlanta, GA. 30350
> (770) 399-9464
>

__________________________________________________
Do you Yahoo!?
Yahoo! Tax Center - File online, calculators, forms, and more
http://tax.yahoo.com

In response to

Browse pgsql-odbc by date

  From Date Subject
Next Message Dave Page 2003-04-03 20:50:48 SQLSetPos
Previous Message Muhammad Shariq 2003-04-03 06:35:35 Re: row-level locking