RE: MS Access Frontend

Thanks Martin. I have decided to go another route. I have nothing but
problems whenever I use Microsoft products. I personally think that
Microsoft was shit when it started, and it is still shit 35 years later. So,
I am just going to take Windows off my computers and put Linux on them and
just use a different client.

Jason L. Amerson

From: Martin Gainty <mgainty(at)hotmail(dot)com>
Sent: Saturday, November 30, 2019 08:02 AM
To: Jason L. Amerson <drjason(at)alphagenius(dot)org>
Subject: Re: MS Access Frontend

Hi Jason

this is how i got the majority of work in the 90s
I have Database X that wont talk to Database Y
you can write a program that
parses the query from <Postgres>
accesses the data from <Access>
inserts to <Progress>

you can save time and $ if you accomplish one of these steps and contract
for the remainder

Makes Sense?
Martin

_____

From: Jason L. Amerson <drjason(at)alphagenius(dot)org
<mailto:drjason(at)alphagenius(dot)org> >
Sent: Friday, November 29, 2019 12:23 PM
To: PostgreSQL <pgsql-general(at)lists(dot)postgresql(dot)org
<mailto:pgsql-general(at)lists(dot)postgresql(dot)org> >
Subject: MS Access Frontend

I am trying to setup MS Access as a frontend so that it would be easier on
my wife and children to interact with PostgreSQL. I looked online for some
tutorials but the ones I found are out-date or only pick up after Access is
connected to PostgreSQL. I was wondering if someone knew of some updated
material that they could point me to or maybe walk me through it. I have
used Access quite a bit years ago and things have changed since then. I know
I must install the ODBC drivers, which I have already done. I have already
setup the DSN and I clicked on test and it says everything is fine. I know
that my next step has something to do with Linked Tables in Access, but I am
not sure how to set it up. I guess that is where I start to need help. The
client computers using the frontend will be running Windows 10 and Office
365, both are updated to the latest versions.

Thank you,

Jason L. Amerson