From: | "David Olbersen" <DOlbersen(at)stbernard(dot)com> |
---|---|
To: | <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: ODBC & Access [Try 2] |
Date: | 2003-04-24 19:54:16 |
Message-ID: | E7E213858379814A9AE48CA6754F5ECB0D6D7F@mail01.stbernard.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Maybe, but I REALLY doubt it.
Like I said, these other tables with very similar structures and very similar data display just fine. It's just this one.
--------------------------
David Olbersen
iGuard Engineer
11415 West Bernardo Court
San Diego, CA 92127
1-858-676-2277 x2152
> -----Original Message-----
> From: Dennis Gearon [mailto:gearond(at)cvc(dot)net]
> Sent: Thursday, April 24, 2003 12:38 PM
> To: David Olbersen
> Cc: pgsql-general(at)postgresql(dot)org
> Subject: Re: [GENERAL] ODBC & Access [Try 2]
>
>
> maybe it's related to sorting in your environment, the
> client's environment, or the server's environment? Case
> sensitive vs. not? (PS, I can't wait till UTF-8 gets totally
> ubiquitous.)
>
> David Olbersen wrote:
> >>-----Original Message-----
> >>From: Jeff Eckermann [mailto:jeff_eckermann(at)yahoo(dot)com]
> >>Sent: Thursday, April 24, 2003 12:08 PM
> >>To: David Olbersen; pgsql-novice(at)postgresql(dot)org
> >>Cc: pgsql-general(at)postgresql(dot)org
> >>Subject: Re: [GENERAL] ODBC & Access [Try 2]
> >>
> >><guess>
> >>Make sure driver option "row versioning" is checked.
> >>Also, make sure that the offending table has a primary
> >>key that Access is recognizing as such.
> >></guess>
> >>If both of those conditions are met, and you still
> >>have a problem, please post your driver settings.
> >
> >
> > Turned on row versioning, no change.
> >
> > When I link the table, Access doesn't ask me to chose the
> primary key. When I look at the Design View for that table
> it's chosen a primary key. The field it's chosen doesn't have
> any NULL values and all the rows for that field are unique,
> so it should be OK, right? The column that it chose is NOT a
> numeric field, but text. Would that cause a problem?
> >
> > Driver settings:
> > ================
> > This is a System DSN.
> >
> > Datasource options (page 1)
> > Disable Genetic Optimizer = Checked
> > KSQO = Checked
> > Recognize Unique Indexes = Checked
> > Use Declare/Fetch = Checked
> > CommLog = Checked
> > Parse Statements = UNchecked
> > Cancel as FreeStmt = UNchecked
> > MyLog = Checked
> > Unknown Sizes = Maximum
> > Data Type Options:
> > Text as LongVarChar = Checked
> > Unknowns as LongVarChar = UNchecked
> > Bools as Char = Checked
> > Miscellanous:
> > Max Varchar = 254
> > Max LongVarChar = 8190
> > Cache Size = 100
> > SysTable Prefixes = dd_;
> >
> > Datasource options (page 2)
> > Read Only = UNchecked
> > Show System Tables = UNchecked
> > LF <-> CR/LF conversion = Checked
> > Updatable Cursors = Checked
> > Row Versioning = Checked (now, wasn't before)
> > Disallow Premature = UNchecked
> > True is -1 = UNchecked
> > Int8 as = default
> > Protocol = 7.x,6.4+
> > OID Options:
> > Show Column = UNchecked
> > Connect Settings = <blank>
> >
> >
> > --------------------------
> > David Olbersen
> > iGuard Engineer
> > 11415 West Bernardo Court
> > San Diego, CA 92127
> > 1-858-676-2277 x2152
> >
> >
> > ---------------------------(end of
> broadcast)---------------------------
> > TIP 1: subscribe and unsubscribe commands go to
> majordomo(at)postgresql(dot)org
> >
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Jean-Luc Lachance | 2003-04-24 19:59:34 | Re: SERIAL type fields |
Previous Message | Bruno Wolff III | 2003-04-24 19:53:04 | Re: SERIAL type fields |