Обсуждение: ODBC & Access [Try 2]

Поиск
Список
Период
Сортировка

ODBC & Access [Try 2]

От
"David Olbersen"
Дата:
I'm trying to use Access as a front end for Postgres. This is
mainly for data-entry and manual updates.

I was able to establish an ODBC connection to the server
without any problems. I was also able to link the tables that
I need. I linked 8 tables total.

7 of them work just fine and I can see all the data in them.
The last one though, only displays '#DELETED' for each column
of each row. I checked the permissions on all the tables and
they're the same -- I have read access (all I need for now, right?)

Any idea what's going on? This is PostgreSQL 7.3.2 on FreeBSD with the PostgreSQL ODBC driver version 7.02.00.05 on Win
XP.

I've also tried the snapshot driver version: 7.03.00.01 with now change. I've also disabled the 'updateable cursors'
optionfor the DSN. 

Any suggestions are more than welcome.

--------------------------
David Olbersen
iGuard Engineer
11415 West Bernardo Court
San Diego, CA 92127
1-858-676-2277 x2152


Re: ODBC & Access [Try 2]

От
"Henshall, Stuart - Design & Print"
Дата:

Try enabling row versioning.
IIRC there's more on http://techdocs.postgresql.org about linking access and some of the problems with like rounding or text/memo.

hth,
- Stuart
P.S. Sorry about the discalimer adder messing with the format :(

> -----Original Message-----
> From: David Olbersen [mailto:DOlbersen@stbernard.com]
>
> I'm trying to use Access as a front end for Postgres. This is
> mainly for data-entry and manual updates.
>
> I was able to establish an ODBC connection to the server
> without any problems. I was also able to link the tables that
> I need. I linked 8 tables total.

> 7 of them work just fine and I can see all the data in them.
> The last one though, only displays '#DELETED' for each column
> of each row. I checked the permissions on all the tables and
> they're the same -- I have read access (all I need for now, right?)
>
> Any idea what's going on? This is PostgreSQL 7.3.2 on FreeBSD
> with the PostgreSQL ODBC driver version 7.02.00.05 on Win XP.
>
> I've also tried the snapshot driver version: 7.03.00.01 with
> now change. I've also disabled the 'updateable cursors'
> option for the DSN.
>
> Any suggestions are more than welcome.
>
> --------------------------
> David Olbersen
> iGuard Engineer
> 11415 West Bernardo Court
> San Diego, CA 92127
> 1-858-676-2277 x2152
>
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 5: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/docs/faqs/FAQ.html
>

DISCLAIMER:The information in this message is confidential and may be legally privileged. It is intended solely for the addressee.  Access to this message by anyone else is unauthorised.  If you are not the intended recipient, any disclosure, copying, or distribution of the message, or any action or omission taken by you in reliance on it, is prohibited and may be unlawful.  Please immediately contact the sender if you have received this message in error. Thank you.

Re: ODBC & Access [Try 2]

От
"David Olbersen"
Дата:
Liam,

> Can I ask you a question? Is your Postgres running on a
> windows machine? or Linux/unix?

FreeBSD.

--------------------------
David Olbersen
iGuard Engineer
11415 West Bernardo Court
San Diego, CA 92127
1-858-676-2277 x2152


> -----Original Message-----
> From: Liam DeMasi [mailto:ldemasi@acsinc-nj.com]
> Sent: Friday, April 25, 2003 7:43 AM
> To: David Olbersen
> Subject: RE: [ODBC] ODBC & Access [Try 2]
>
>
>
> Hello,
>
> Can I ask you a question? Is your Postgres running on a
> windows machine? or Linux/unix?
>
> -----Original Message-----
> From: pgsql-odbc-owner@postgresql.org
> [mailto:pgsql-odbc-owner@postgresql.org]On Behalf Of David Olbersen
> Sent: Friday, April 25, 2003 10:36 AM
> To: pgsql-odbc@postgresql.org
> Subject: [ODBC] ODBC & Access [Try 2]
>
>
> I'm trying to use Access as a front end for Postgres. This is
> mainly for data-entry and manual updates.
>
> I was able to establish an ODBC connection to the server
> without any problems. I was also able to link the tables that
> I need. I linked 8 tables total.
>
> 7 of them work just fine and I can see all the data in them.
> The last one though, only displays '#DELETED' for each column
> of each row. I checked the permissions on all the tables and
> they're the same -- I have read access (all I need for now, right?)
>
> Any idea what's going on? This is PostgreSQL 7.3.2 on FreeBSD
> with the PostgreSQL ODBC driver version 7.02.00.05 on Win XP.
>
> I've also tried the snapshot driver version: 7.03.00.01 with
> now change. I've also disabled the 'updateable cursors'
> option for the DSN.
>
> Any suggestions are more than welcome.
>
> --------------------------
> David Olbersen
> iGuard Engineer
> 11415 West Bernardo Court
> San Diego, CA 92127
> 1-858-676-2277 x2152
>
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 5: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/docs/faqs/FAQ.html
>


Re: ODBC & Access [Try 2]

От
"David Olbersen"
Дата:
Stuart,
 
Row versioning didn't make any difference.
 
Looking to Microsoft for help (ugh) I found this article:
 
 
Which didn't really help that much. It seems to say the problem is with Access 2.0 or 97 or some such. But I'm using Access 2000!
 
I may just have to give up on this one and find some other way of doing this.


David Olbersen
iGuard Engineer
11415 West Bernardo Court
San Diego, CA 92127
1-858-676-2277 x2152

-----Original Message-----
From: Henshall, Stuart - Design & Print [mailto:SHenshall@westcountry-design-print.co.uk]
Sent: Friday, April 25, 2003 7:40 AM
To: David Olbersen
Cc: pgsql-odbc@postgresql.org
Subject: RE: [ODBC] ODBC & Access [Try 2]

Try enabling row versioning.
IIRC there's more on http://techdocs.postgresql.org about linking access and some of the problems with like rounding or text/memo.

hth,
- Stuart
P.S. Sorry about the discalimer adder messing with the format :(

> -----Original Message-----
> From: David Olbersen [mailto:DOlbersen@stbernard.com]
>
> I'm trying to use Access as a front end for Postgres. This is
> mainly for data-entry and manual updates.
>
> I was able to establish an ODBC connection to the server
> without any problems. I was also able to link the tables that
> I need. I linked 8 tables total.

> 7 of them work just fine and I can see all the data in them.
> The last one though, only displays '#DELETED' for each column
> of each row. I checked the permissions on all the tables and
> they're the same -- I have read access (all I need for now, right?)
>
> Any idea what's going on? This is PostgreSQL 7.3.2 on FreeBSD
> with the PostgreSQL ODBC driver version 7.02.00.05 on Win XP.
>
> I've also tried the snapshot driver version: 7.03.00.01 with
> now change. I've also disabled the 'updateable cursors'
> option for the DSN.
>
> Any suggestions are more than welcome.
>
> --------------------------
> David Olbersen
> iGuard Engineer
> 11415 West Bernardo Court
> San Diego, CA 92127
> 1-858-676-2277 x2152
>
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 5: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/docs/faqs/FAQ.html
>

DISCLAIMER:The information in this message is confidential and may be legally privileged. It is intended solely for the addressee.  Access to this message by anyone else is unauthorised.  If you are not the intended recipient, any disclosure, copying, or distribution of the message, or any action or omission taken by you in reliance on it, is prohibited and may be unlawful.  Please immediately contact the sender if you have received this message in error. Thank you.

Re: ODBC & Access [Try 2]

От
"Henshall, Stuart - Design & Print"
Дата:
If you send the table definition I will see if I can get it to work here.
- Stuart
-----Original Message-----
From: David Olbersen [mailto:DOlbersen@stbernard.com]
Sent: 25 April 2003 16:09
To: pgsql-odbc@postgresql.org
Subject: Re: [ODBC] ODBC & Access [Try 2]

Stuart,
 
Row versioning didn't make any difference.
 
Looking to Microsoft for help (ugh) I found this article:
 
 
Which didn't really help that much. It seems to say the problem is with Access 2.0 or 97 or some such. But I'm using Access 2000!
 
I may just have to give up on this one and find some other way of doing this.


David Olbersen
iGuard Engineer
11415 West Bernardo Court
San Diego, CA 92127
1-858-676-2277 x2152

-----Original Message-----
From: Henshall, Stuart - Design & Print [mailto:SHenshall@westcountry-design-print.co.uk]
Sent: Friday, April 25, 2003 7:40 AM
To: David Olbersen
Cc: pgsql-odbc@postgresql.org
Subject: RE: [ODBC] ODBC & Access [Try 2]

Try enabling row versioning.
IIRC there's more on http://techdocs.postgresql.org about linking access and some of the problems with like rounding or text/memo.

hth,
- Stuart
P.S. Sorry about the discalimer adder messing with the format :(

> -----Original Message-----
> From: David Olbersen [mailto:DOlbersen@stbernard.com]
>
> I'm trying to use Access as a front end for Postgres. This is
> mainly for data-entry and manual updates.
>
> I was able to establish an ODBC connection to the server
> without any problems. I was also able to link the tables that
> I need. I linked 8 tables total.

> 7 of them work just fine and I can see all the data in them.
> The last one though, only displays '#DELETED' for each column
> of each row. I checked the permissions on all the tables and
> they're the same -- I have read access (all I need for now, right?)
>
> Any idea what's going on? This is PostgreSQL 7.3.2 on FreeBSD
> with the PostgreSQL ODBC driver version 7.02.00.05 on Win XP.
>
> I've also tried the snapshot driver version: 7.03.00.01 with
> now change. I've also disabled the 'updateable cursors'
> option for the DSN.
>
> Any suggestions are more than welcome.
>
> --------------------------
> David Olbersen
> iGuard Engineer
> 11415 West Bernardo Court
> San Diego, CA 92127
> 1-858-676-2277 x2152
>
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 5: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/docs/faqs/FAQ.html
>

DISCLAIMER:The information in this message is confidential and may be legally privileged. It is intended solely for the addressee.  Access to this message by anyone else is unauthorised.  If you are not the intended recipient, any disclosure, copying, or distribution of the message, or any action or omission taken by you in reliance on it, is prohibited and may be unlawful.  Please immediately contact the sender if you have received this message in error. Thank you.



DISCLAIMER:The information in this message is confidential and may be legally privileged. It is intended solely for the addressee. Access to this message by anyone else is unauthorised. If you are not the intended recipient, any disclosure, copying, or distribution of the message, or any action or omission taken by you in reliance on it, is prohibited and may be unlawful. Please immediately contact the sender if you have received this message in error. Thank you.

Re: ODBC & Access [Try 2]

От
"Hiroshi Inoue"
Дата:
Did you try to uncheck the *Text as LongVarChar* DSN option ?
 
regards,
Hiroshi Inoue
-----Original Message-----
From: David Olbersen

Stuart,
 
Row versioning didn't make any difference.
 
Looking to Microsoft for help (ugh) I found this article:
 
 
Which didn't really help that much. It seems to say the problem is with Access 2.0 or 97 or some such. But I'm using Access 2000!
 
I may just have to give up on this one and find some other way of doing this.


Re: ODBC & Access [Try 2]

От
"David Olbersen"
Дата:
That did it!
 
Thank you everybody for your input!


David Olbersen
iGuard Engineer
11415 West Bernardo Court
San Diego, CA 92127
1-858-676-2277 x2152

-----Original Message-----
From: Hiroshi Inoue [mailto:inoue@tpf.co.jp]
Sent: Friday, April 25, 2003 8:59 AM
To: David Olbersen
Cc: pgsql-odbc@postgresql.org
Subject: RE: [ODBC] ODBC & Access [Try 2]

Did you try to uncheck the *Text as LongVarChar* DSN option ?
 
regards,
Hiroshi Inoue
-----Original Message-----
From: David Olbersen

Stuart,
 
Row versioning didn't make any difference.
 
Looking to Microsoft for help (ugh) I found this article:
 
 
Which didn't really help that much. It seems to say the problem is with Access 2.0 or 97 or some such. But I'm using Access 2000!
 
I may just have to give up on this one and find some other way of doing this.