I was giving a minimalist answer here, so as not to imply that a
lot of software *had to be written* to use Access as a simple
retreival tool for Postgres. I have trained numerous clients to
use the Linked Table Manager who have little more than 'some
Excel experience'. Certainly, the possibilities you mention are
desirable in many situations, but they would require a
significant level of knowledge to implement.
terry
>> You are quite correct. However, that assumes a certain level
>> of knowledge and confidence in the end-user. That works fine
>> if you are just doing it for yourself, but if you are writing
>> it for others, why not make it as easy as practical? Besides,
>> there are other advantages. I can have the user login to the
>> database via a form, and then add or remove the linked
>> tables/views as required based on PostgreSQL ACL's. This
>> allows a single copy of the application to work in a
>> multi-user fashion, as well as allowing me to update the
>> structure of the clients remotely, in a fashion. Being able
>> to control the client so well remotely makes maintenance and
>> updates in a client-server environment much more manageable.
>> If I add some more views, I don't have to tell a thousand
>> people to link the new views and deal with the resultant
>> problems. It will be done automatically the next time they
>> login.
>>
>> Mark Taff
>>
>> -----Original Message-----
>> From: Terry [mailto:tg5027@citlink.net]
>> Sent: Tuesday, February 12, 2002 12:59 PM
>> To: Mark A. Taff
>> Subject: Re: [ODBC] Windows client?
>>
>> >> If you are looking for something for end-users, you can
>> >> use MS-Access as a client to a PostgreSQL server, by
>> >> linking tables (this can be done with VBA code).
>>
>> You don't need code to link via ODBC, just use File menu, Get
>> External Data, Link Tables. Select ODBC as the data source
>> and follow the wizards..
--
Terry