pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
MS Access and PostgreSQL
3+ messages / 2 participants
[nested] [flat]

* MS Access and PostgreSQL
@ 2006-04-07 19:45 C K <shreeseva.it@gmail.com>
  2006-04-07 20:00 ` Re: MS Access and PostgreSQL James Herbers <james@herbers.ca>
  0 siblings, 1 reply; 3+ messages in thread

From: C K @ 2006-04-07 19:45 UTC (permalink / raw)
  To: pgsql-admin

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



^ permalink  raw  reply  [nested|flat] 3+ messages in thread

* Re: MS Access and PostgreSQL
  2006-04-07 19:45 MS Access and PostgreSQL C K <shreeseva.it@gmail.com>
@ 2006-04-07 20:00 ` James Herbers <james@herbers.ca>
  2006-04-15 08:59   ` Re: MS Access and PostgreSQL C K <shreeseva.it@gmail.com>
  0 siblings, 1 reply; 3+ messages in thread

From: James Herbers @ 2006-04-07 20:00 UTC (permalink / raw)
  To: C K <shreeseva.it@gmail.com>; +Cc: pgsql-admin

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
>   




^ permalink  raw  reply  [nested|flat] 3+ messages in thread

* Re: MS Access and PostgreSQL
  2006-04-07 19:45 MS Access and PostgreSQL C K <shreeseva.it@gmail.com>
  2006-04-07 20:00 ` Re: MS Access and PostgreSQL James Herbers <james@herbers.ca>
@ 2006-04-15 08:59   ` C K <shreeseva.it@gmail.com>
  0 siblings, 0 replies; 3+ messages in thread

From: C K @ 2006-04-15 08:59 UTC (permalink / raw)
  To: James Herbers <james@herbers.ca>; +Cc: pgsql-admin

Thanks you. I found it very useful and solved my problem.
Thanks.
CPK



^ permalink  raw  reply  [nested|flat] 3+ messages in thread


end of thread, other threads:[~2006-04-15 08:59 UTC | newest]

Thread overview: 3+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2006-04-07 19:45 MS Access and PostgreSQL C K <shreeseva.it@gmail.com>
2006-04-07 20:00 ` James Herbers <james@herbers.ca>
2006-04-15 08:59   ` C K <shreeseva.it@gmail.com>

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox