Re: No Current Record

From: Jeff Eckermann <jeff_eckermann(at)yahoo(dot)com>
To: Guy Steven <guy(at)wanakalaw(dot)co(dot)nz>
Cc: pgsql-odbc(at)postgresql(dot)org
Subject: Re: No Current Record
Date: 2004-01-08 15:42:02
Message-ID: 20040108154202.22584.qmail@web20812.mail.yahoo.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-odbc

--- Greg Campbell <greg(dot)campbell(at)us(dot)michelin(dot)com>
wrote:
> Troubleshoot how Access sees your table.
> In Access, choose to view the design of your table
> and ignore messages
> about that you will not be able to change things on
> a linked table. Are
> the fields what you think they should be numeric and
> character.
>
> Does your table have a primary key? It should.
> Is the postgres primary key float or int8 or
> serial8? That would be bad.
> Access/ODBC behaves best when your fields are int
> (int4) or serial
> (serial4). There is some indication that adding a
> timestamp field with
> a time of NOW() will allow Access to determine its
> (client) view of key
> matches the Postgres servers view of the key and
> match records for
> updating, etc. -- otherwise you tend to get
> non-updatable recordsets.

If you use "timestamp" for any data field that will be
used by Access, be sure to make it "timestamp(0)",
i.e. no fractional seconds: Access doesn't like them.

>
> There is some indication that tables that HAVE
> record OIDs help maintain
> the client-server key connection, avoiding the "no
> current record
> problems".

Make sure that you have "row versioning" checked in
the ODBC driver options for your DSN.

>
> I am a littles surprised at the ability to delete.
> Access tends to use a
> syntax of 'DELETE * FROM table' where Postgres
> insist on 'DELETE FROM
> table' with no *. I have to use pass-throughs to
> delete records.

I am more than a little surprised at this. For me,
Access accepts the "delete from table" syntax just
fine.
>
> I not sure any of this will help but I figure it is
> worth a shot.
>
>
> Guy Steven wrote:
> >
> > I am experiencing a very frustrating problem with
> postgresql and access
> > 2000.
> >
> > I have a postgresql 7.2.4-5.80 database and am
> accessing it using access
> > 2000.
> > Tables are linked using odbc.
> >
> > I can read a table. I can add records to a table.
> I can edit and delete
> > existing records in the table, but I can not edit
> or delete records in the
> > table that were added using the odbc connection.
> By this I mean that records
> > that are imported into the postgresql (from a dump
> from pg_dump) can be
> > edited or deleted, but if I add a record from
> access, I can't edit or delete
> > from access.
> > From within psql the records look identical.
> > The error message I get is No Current Record.

I've never seen this error. I suggest searching in
the MS Knowledge Base and on Access groups, using the
error string, to get more information about what
triggers that error.

FWIW, most of us find that Access and PostgreSQL get
along just fine, subject to a small number of gotchas
which are fairly easily worked around (check the ODBC
driver site on http://gborg.postgresql.org for more
information). If you don't find a solution based on
the above, please post your ODBC driver settings,
along with the table definitions for the tables that
are giving you problems.

__________________________________
Do you Yahoo!?
Yahoo! Hotjobs: Enter the "Signing Bonus" Sweepstakes
http://hotjobs.sweepstakes.yahoo.com/signingbonus

In response to

Browse pgsql-odbc by date

  From Date Subject
Next Message Guy Steven 2004-01-09 00:14:59 Re: No Current Record
Previous Message Greg Campbell 2004-01-08 14:40:39 Re: No Current Record