From: Byron Nikolaidis <byronn@solipsys.com>
To: Moray McConnachie <Moray.McConnachie@computing-services.oxford.ac.uk>
Cc: pgsql-interfaces@postgreSQL.org
Subject: Re: [INTERFACES] Access 2000
Date: Mon, 23 Aug 1999 12:43:57 -0400
Message-ID: <37C17A4D.C69C91BB@solipsys.com> (raw)
References: <37C173E6.2A1F45F3@solipsys.com>
<3.0.5.32.19990823163802.0079f180@199.107.2.1>
<EXECMAIL.990823172859.J@moraypc.computing-services.oxford.ac.uk>
Moray McConnachie wrote:
> On Mon, 23 Aug 1999 12:16:38 -0400 Byron Nikolaidis
> <byronn@solipsys.com> wrote:
>
> >
> >
> > Michael Doyle wrote:
> >
> > > I need help with Access 2000 and PostgreSQL...
> > >
> > > I have several databases running on my server (It's a FreeBSD server
> > > running Postgress 6.4) and Access 95 had no trouble acting as a
> > > front end to these databases
> > >
> > > However, I cannot create new Access 2000 databases to see either new
> > > or old databases on the server.
> > >
> > > Curiously, upgrading the Access 95 databases to Access 2000 lets them
> > > continue to see the linked tables.
> > >
> > > Something strange is going on with Access 2000 and ODBC interfaces.
> > > Any ideas on how to resolve this ?
> > >
> >
> > Do you see any error messages, either on screen or in any of the logfiles?
>
> Michael's problem is basically the same as I posted a few
> weeks back, and others have contacted me about it since. It
> appears to leave no error messages, but frankly I've given
> up and have no longer been looking.
>
> Some have said that all 3rd party ODBC drivers have had to
> be rewritten to co-operate with Access 2000's
> implementatation of ODBC, which is hardly brilliant!
>
> I put in a bug report to Microsoft, but so far no response.
>
> ----------------------
> Moray.McConnachie@computing-services.oxford.ac.uk
It figures. Unfortunately, I really don't have the money to go out and buy
Access 2000, just to try and figure out what's different.
The real problem is that the ODBC spec is so overloaded and fat. Its verbose,
and yet there are so many variations for getting at data, that it is actually
very difficult to make sure that every possible contingency is correct in the
driver.
And that was just odbc version 2.x. ODBC Version 3.x is a real heart-warmer!
And I can't wait to see what version 4.x might bring!!! Of course, they all
have to be backward-compatible with odbc version 1.0 ;)
Byron
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-interfaces@postgresql.org
Cc: byronn@solipsys.com, Moray.McConnachie@computing-services.oxford.ac.uk
Subject: Re: [INTERFACES] Access 2000
In-Reply-To: <37C17A4D.C69C91BB@solipsys.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox