Hi,
I'm using access as the front-end to a postgreSQL database using odbc, and I'm looking for the best way to talk to the database. I don't want to use directly linked tables because the sql that gets generated isn't really optimised for postgreSQL, so I'm looking at ADO, pass-through queries etc.
When I create a bound form based on a pass-through query, I can't edit any of the fields, which I understand because pass-through queries aren't updateable, but: is there any way to base a bound form on a pass-through query, allow the fields to be edited, but then catch the update in an event, and send my own SQL to the database for the update? It would just be nice to be able to create bound forms to start with, rather than having to go through setting all the fields when the form loads or whatever.
Cheers for any pointers!
I'm using access as the front-end to a postgreSQL database using odbc, and I'm looking for the best way to talk to the database. I don't want to use directly linked tables because the sql that gets generated isn't really optimised for postgreSQL, so I'm looking at ADO, pass-through queries etc.
When I create a bound form based on a pass-through query, I can't edit any of the fields, which I understand because pass-through queries aren't updateable, but: is there any way to base a bound form on a pass-through query, allow the fields to be edited, but then catch the update in an event, and send my own SQL to the database for the update? It would just be nice to be able to create bound forms to start with, rather than having to go through setting all the fields when the form loads or whatever.
Cheers for any pointers!