I have a PostgreSQL database working as backend and I have to develop an Access frontend solution for regular users of this database.

I decided it best to create some forms to manage the input, delition and deletion of data in the datbases, but as I am somewhat new to Access I may not be righ in my assumption here: if I import tables from the database into Access using the linked-table facility, and if I specify such connection as read-only (I want them to use the forms and the forms alone, least they screw everything up), when using the forms, they would connect to my Access's access of the tables, which is read-only, and thus edition, addition and deletion will not be supported for the form, right?

As I though of this, I also thought of creating a button on the form to change the table it is connected and bound to. Basically, it would open an ODBC connection to the real database and bind the form to the same table, but using different access rights.

Here comes the real question: how viable/useful/helpful/problem-solving is this solution and what VBA elements would I need to use? (I just learned about macros and VBA the last week)

  • wiki.postgresql.org/wiki/… – McNets Nov 22 '16 at 9:58
  • there are a lot of tools to use with postgresql. – McNets Nov 22 '16 at 9:58
  • @McNets I have to use access as the front end. Now, knowing this, I have explained my concern and a "plausible" way to create a workaround, and asked for someone with a larger expertise than me if it is a valid approach and what I would need to develop it or if there is a different way to come around this. – Feillen Nov 22 '16 at 10:02
  • @Feillen I know, but my experiences with MS-Access is not really good. Of course it's an easy way to design forms, but it's really expensive. Have you considered LibreOffice? – McNets Nov 22 '16 at 10:20

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.