Re: Using PostgreSQL and Access? - Mailing list pgsql-general

From Markus Meyer
Subject Re: Using PostgreSQL and Access?
Date
Msg-id HKECJNLJKDOEECLAOOJDEEHICDAA.meyer@mesw.de
Whole thread Raw
In response to Re: Using PostgreSQL and Access?  ("Kevin J. Drewiske" <drewiskk@msoe.edu>)
List pgsql-general
Dear Kevin,

many thanks for your reply. It would really be fine, if you could send me
this 'ODBC installation manual'. I have been working with Access for many
years, but I'm just getting started using PostgreSQL. Because the databases
of some of my customers are constantly growing, I want to install them
PostgreSQL as a new backend.

Which tool do you use for importing data / table definitions into Access?
I've found a script on the net for that purpose, but it doesn't seem to work
well, so I'm likely to write my own script and maybe write a patch for the
ODBC driver to accomplish an "Access compatibility mode". Everything will,
of course, be put into the public domain.

Some goals that I would like to accomplish, are:

- Making editing behave more like Access (serial keys are created on first
keystroke etc.)
- Make the ODBC driver to make Access use the correct primary index (this
_must_ be possible!)
- Making queries act more like Access does (case-insensitive, but correct
uppercase / lowercase is returned
- Have a nice installation program on Windoze, that does all the cygwin/psql
installation stuff, just as MySQL has
- Whatever is necessary to make PostgreSQL a _real_ alternative to SQL
server on Windoze

Maybe I'm just dreaming with some of these points, and maybe my work would
be useless because there are already good tools out there that I don't know
of.

Any suggestions, donations, help? ;-)


Markus

> -----Ursprungliche Nachricht-----
> Von: Kevin J. Drewiske [mailto:drewiskk@msoe.edu]
> Gesendet: Donnerstag, 25. Oktober 2001 05:22
> An: 'Markus Meyer'; PostgreSQL (General) Mailing List
> Betreff: RE: Using PostgreSQL and Access?
>
>
> I've been using an MS Access front-end with Postgres on Digital Unix,
> Redhat and Mandrake with fairly good results.  We started on v6.5.3 and
> just upgraded to 7.1.3.
>
> I download the ODBC driver from odbc.postgresql.org and haven't had any
> problems.  The duplicate error could possibly because Access cannot
> identify a unique record.  A 'many' table in a one to many relationship
> could cause this problem if the foreign key is 'keyed' rather
> than a unique
> key (which I implement similar to Access' auto number).  You may want to
> show the OID column (Advanced Settings).
>
> If you would like, I have prepared an 'ODBC installation manual' that I
> have in PDF format that contains graphics/screenshots for the individual
> settings.  Please contact me directly if you would like to obtain this
> file.
>
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> Kevin Drewiske '01 CE
> MSOE Webmaster Team: http://www.msoe.edu/
> KJDesign Website Development: http://www.drewiske.com/KJDesign/
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
> -----Original Message-----
> From:    Markus Meyer [SMTP:meyer@mesw.de]
> Sent:    Wednesday, October 24, 2001 18:29
> To:    PostgreSQL (General) Mailing List
> Subject:    Using PostgreSQL and Access?
>
> Since the PostgreSQL (CygWin) mailing list seems to be quite dead, I'm
> posting this one here.
>
> My question is: Has any one successfully used PostgreSQL with Access? I
> have
> read the Accces-FAQ, but I still have major problems: When I create a form
> and change / add some data in there, I always get errors, f.e. "Cannot add
> duplicate index" (although I did just a minor change), but also
> other error
> messages, or data conversion errors ("Cannot convert XID to int4"). The
> error messages change, if I try other settings in ODBC driver, but it
> doesn't work either. Also I get the error messages about the unique index
> when I add a new record as described in the ODBC FAQ, but I don't agree
> with
> the "workaround" by using a timestamp. That one is really weird, and it
> really should work without.
>
> Maybe PostgreSQL (or the ODBC driver) should have a
> "compatibility" mode to
> work with more forgiving frontends. I don't see, why f.e. a boolean column
> gives an error, if you do something like "boolean_col = 0".
>
> Access does work well with other databases over ODBC (okay, SQL Server
> works, but also MySQL), so why doesn't PostgreSQL?
>
> Regards
>
>
> Markus
>
>
> ----------------------------------------------------
> Sign Up for NetZero Platinum Today
> Only $9.95 per month!
> http://my.netzero.net/s/signup?r=platinum&refcd=PT97
>


pgsql-general by date:

Previous
From: Fran Fabrizio
Date:
Subject: Triggers after insert
Next
From: qk22@gmx.co.uk
Date:
Subject: Re: Can not input large text data -- problem solved --Thank you!