Microsoft has a KB article here -
http://support.microsoft.com/kb/q128809/ - you may want to look at. I
found the best way to avoid this was to use pass-through queries.
J Herbers
C K wrote:
> Dear Friends,
> I am here for a problem regarding MS Access and PostgreSQL connection
> through ODBC. I have liked my PostgreSQL database tables to MS Access.
> When I am going for inserting/updating any data is just displays
> #deleted. I also use MySQL (client's choice). Same problem occurs for
> MySQL also. But when I set the 'Return matching rows' option from
> MyODBC 3.51.12 interface. the problem mostly gets solved. Other things
> required are PK (or Unique column), a timestamp etc. I have done all
> these for POstgreSQL, but it doen't work. Is there any option as
> 'Return matching rows' for PGODBC? Or How I can solve this problem?
> Please help.
> Thanks and Regards.
> CPK
>
> ---------------------------(end of broadcast)---------------------------
> TIP 9: In versions below 8.0, the planner will ignore your desire to
> choose an index scan if your joining column's datatypes do not
> match
>
