Thread: Access 97 and pgsqlodbc version 7.03.0100
There are two separate problems I am having -
1. You can connect any table in Access 97 and use it in that session but if
you close the database (mdb file) and open it again you get a GPF on opening
the table.
It seems to happen with which ever table I open. I think it must be a
problem with the ODBC 3 driver because I didn't have this problem before
upgrading.
2. This problem is more interesting:
I have a table similar to :
CREATE TABLE public.subs (
subcontractorid varchar(10),
"payment number blue" int2,
description text
);
I link it into Access 97 and open the table. It opens correctly, but after
approx 8 seconds all the data turns to #Name? . I've looked at the
mylog_xxx.log file and have found the following:
[3704]send_query(): conn=42153888, query='SELECT "subcontractorid","payment
'#S_C_H#' blue","description1","xmin" FROM "public"."subs2" WHERE
"subcontractorid" = 'ARB' OR "subcontractorid" = 'ARCMOR' OR
"subcontractorid" = 'ARROW' OR "subcontractorid" = 'ASBESTEC' OR
"subcontractorid" = 'ASH' OR "subcontractorid" = 'ashbrook' OR
"subcontractorid" = 'ASHCROFT' OR "subcontractorid" = 'ASPHALTIC' OR
"subcontractorid" = 'ASSOCIATED' OR "subcontractorid" = 'ATLAS''
as you can see "payment number blue" has been replaced by "payment '#S_C_H#'
blue" I assumed from this that the word 'number' was the problem so renamed
the field "pay no blue" but I still get the problem.
Any Ideas?
BTW I am using Postgres 7.3.2 on Mandrake linux 8.1, Windows XP sp1, Access
97 sr2
Regards,
Ben
_________________________________________________________________
Surf together with new Shared Browsing
http://join.msn.com/?page=features/browse&pgmarket=en-gb&XAPID=74&DI=1059
Please remove spaces from the column name.
Ben Trewern wrote:
>
> There are two separate problems I am having -
>
> 1. You can connect any table in Access 97 and use it in that session but if
> you close the database (mdb file) and open it again you get a GPF on opening
> the table.
>
> It seems to happen with which ever table I open. I think it must be a
> problem with the ODBC 3 driver because I didn't have this problem before
> upgrading.
>
> 2. This problem is more interesting:
>
> I have a table similar to :
>
> CREATE TABLE public.subs (
> subcontractorid varchar(10),
> "payment number blue" int2,
> description text
> );
>
> I link it into Access 97 and open the table. It opens correctly, but after
> approx 8 seconds all the data turns to #Name? . I've looked at the
> mylog_xxx.log file and have found the following:
>
> [3704]send_query(): conn=42153888, query='SELECT "subcontractorid","payment
> '#S_C_H#' blue","description1","xmin" FROM "public"."subs2" WHERE
> "subcontractorid" = 'ARB' OR "subcontractorid" = 'ARCMOR' OR
> "subcontractorid" = 'ARROW' OR "subcontractorid" = 'ASBESTEC' OR
> "subcontractorid" = 'ASH' OR "subcontractorid" = 'ashbrook' OR
> "subcontractorid" = 'ASHCROFT' OR "subcontractorid" = 'ASPHALTIC' OR
> "subcontractorid" = 'ASSOCIATED' OR "subcontractorid" = 'ATLAS''
>
> as you can see "payment number blue" has been replaced by "payment '#S_C_H#'
> blue" I assumed from this that the word 'number' was the problem so renamed
> the field "pay no blue" but I still get the problem.
>
> Any Ideas?
>
> BTW I am using Postgres 7.3.2 on Mandrake linux 8.1, Windows XP sp1, Access
> 97 sr2
regards,
Hiroshi Inoue
http://www.geocities.jp/inocchichichi/psqlodbc/
mylog as requested. Ben >From: Hiroshi Inoue <Inoue@tpf.co.jp> >To: Ben Trewern <ben_trewern@hotmail.com> >CC: pgsql-odbc@postgresql.org >Subject: Re: [ODBC] Access 97 and pgsqlodbc version 7.03.0100 >Date: Tue, 20 May 2003 17:31:18 +0900 > >Ben Trewern wrote: > > > > Thanks, > > > > Is this a problem with the odbc driver or Access 97 as > > I'll be changing to access XP very soon? > >Maybe the Access 97 problem. I'm using Access 200 and see >no #S_C_H# for your example table. > > > BTW is there any fix for the GPF problem, or should I go > > back to using the ODBC 2.5 legacy driver? > >Could you send me the Mylog output for the crash case ? > >regards, >Hiroshi Inoue > http://www.geocities.jp/inocchichichi/psqlodbc/ _________________________________________________________________ Stay in touch with absent friends - get MSN Messenger http://www.msn.co.uk/messenger
Attachment
Thanks, Is this a problem with the odbc driver or Access 97 as I'll be changing to access XP very soon? BTW is there any fix for the GPF problem, or should I go back to using the ODBC 2.5 legacy driver? Thanks again, Ben >From: Hiroshi Inoue <Inoue@tpf.co.jp> >To: Ben Trewern <ben_trewern@hotmail.com> >CC: pgsql-odbc@postgresql.org >Subject: Re: [ODBC] Access 97 and pgsqlodbc version 7.03.0100 >Date: Tue, 20 May 2003 09:50:28 +0900 > >Please remove spaces from the column name. > >Ben Trewern wrote: > > > > There are two separate problems I am having - > > > > 1. You can connect any table in Access 97 and use it in that session >but if > > you close the database (mdb file) and open it again you get a GPF on >opening > > the table. > > > > It seems to happen with which ever table I open. I think it must be a > > problem with the ODBC 3 driver because I didn't have this problem before > > upgrading. > > > > 2. This problem is more interesting: > > > > I have a table similar to : > > > > CREATE TABLE public.subs ( > > subcontractorid varchar(10), > > "payment number blue" int2, > > description text > > ); > > > > I link it into Access 97 and open the table. It opens correctly, but >after > > approx 8 seconds all the data turns to #Name? . I've looked at the > > mylog_xxx.log file and have found the following: > > > > [3704]send_query(): conn=42153888, query='SELECT >"subcontractorid","payment > > '#S_C_H#' blue","description1","xmin" FROM "public"."subs2" WHERE > > "subcontractorid" = 'ARB' OR "subcontractorid" = 'ARCMOR' OR > > "subcontractorid" = 'ARROW' OR "subcontractorid" = 'ASBESTEC' OR > > "subcontractorid" = 'ASH' OR "subcontractorid" = 'ashbrook' OR > > "subcontractorid" = 'ASHCROFT' OR "subcontractorid" = 'ASPHALTIC' OR > > "subcontractorid" = 'ASSOCIATED' OR "subcontractorid" = 'ATLAS'' > > > > as you can see "payment number blue" has been replaced by "payment >'#S_C_H#' > > blue" I assumed from this that the word 'number' was the problem so >renamed > > the field "pay no blue" but I still get the problem. > > > > Any Ideas? > > > > BTW I am using Postgres 7.3.2 on Mandrake linux 8.1, Windows XP sp1, >Access > > 97 sr2 > >regards, >Hiroshi Inoue > http://www.geocities.jp/inocchichichi/psqlodbc/ > >---------------------------(end of broadcast)--------------------------- >TIP 5: Have you checked our extensive FAQ? > >http://www.postgresql.org/docs/faqs/FAQ.html _________________________________________________________________ Find a cheaper internet access deal - choose one to suit you. http://www.msn.co.uk/internetaccess
Ben Trewern wrote:
>
> Thanks,
>
> Is this a problem with the odbc driver or Access 97 as
> I'll be changing to access XP very soon?
Maybe the Access 97 problem. I'm using Access 200 and see
no #S_C_H# for your example table.
> BTW is there any fix for the GPF problem, or should I go
> back to using the ODBC 2.5 legacy driver?
Could you send me the Mylog output for the crash case ?
regards,
Hiroshi Inoue
http://www.geocities.jp/inocchichichi/psqlodbc/
Please try the snapshot(7.03.0102) dll at http://www.geocities.jp/inocchichichi/psqlodbc/ . > -----Original Message----- > From: Ben Trewern [mailto:ben_trewern@hotmail.com] > Sent: Tuesday, May 20, 2003 5:45 PM > To: Inoue@tpf.co.jp > Cc: pgsql-odbc@postgresql.org > Subject: Re: [ODBC] Access 97 and pgsqlodbc version 7.03.0100 > > > mylog as requested. regards, Hiroshi Inoue http://www.geocities.jp/inocchichichi/psqlodbc/
This seems to have fixed the GPF problem but now if I look at a Master -
Detail form I get #Deleted in some of the fields in the detail subform:
Field1 Field2 Descripton1 Field4 Field5
----------------------------------------------------------------------------------
10 1/1/03 Description OK 1000.00 1.148
#Deleted #Deleted Description OK #Deleted #Deleted
#Deleted #Deleted Description OK #Deleted #Deleted
I'm not sure if the above will look OK on your e-mail client but it is meant
to show the first line OK but the following lines have #Deleted everywhere
except the Description1 field which is a memo.
I hope this helps
I'll send you a mylog direct.
Regards,
Ben
>From: "Hiroshi Inoue" <Inoue@tpf.co.jp>
>To: "Ben Trewern" <ben_trewern@hotmail.com>
>CC: <pgsql-odbc@postgresql.org>
>Subject: Re: [ODBC] Access 97 and pgsqlodbc version 7.03.0100
>Date: Wed, 21 May 2003 01:13:50 +0900
>
>Please try the snapshot(7.03.0102) dll at
>http://www.geocities.jp/inocchichichi/psqlodbc/ .
>
> > -----Original Message-----
> > From: Ben Trewern [mailto:ben_trewern@hotmail.com]
> > Sent: Tuesday, May 20, 2003 5:45 PM
> > To: Inoue@tpf.co.jp
> > Cc: pgsql-odbc@postgresql.org
> > Subject: Re: [ODBC] Access 97 and pgsqlodbc version 7.03.0100
> >
> >
> > mylog as requested.
>
>regards,
>Hiroshi Inoue
>http://www.geocities.jp/inocchichichi/psqlodbc/
>
>
>---------------------------(end of broadcast)---------------------------
>TIP 2: you can get off all lists at once with the unregister command
> (send "unregister YourEmailAddressHere" to majordomo@postgresql.org)
_________________________________________________________________
Overloaded with spam? With MSN 8, you can filter it out
http://join.msn.com/?page=features/junkmail&pgmarket=en-gb&XAPID=32&DI=1059
Ben Trewern wrote:
>
> This seems to have fixed the GPF problem but now if I look at a Master -
> Detail form I get #Deleted in some of the fields in the detail subform:
>
> Field1 Field2 Descripton1 Field4 Field5
> ----------------------------------------------------------------------------------
> 10 1/1/03 Description OK 1000.00 1.148
> #Deleted #Deleted Description OK #Deleted #Deleted
> #Deleted #Deleted Description OK #Deleted #Deleted
>
> I'm not sure if the above will look OK on your e-mail client but it is meant
> to show the first line OK but the following lines have #Deleted everywhere
> except the Description1 field which is a memo.
Do you create an unique index on the table or specify a
really unique identifier for the table ?
regards,
Hiroshi Inoue
http://www.geocities.jp/inocchichichi/psqlodbc/
The Master table Primary key is varchar(10) but the detail table has a varchar(50) as the joined field. I'll try changing it now. Regards, Ben >From: Hiroshi Inoue <Inoue@tpf.co.jp> >To: Ben Trewern <ben_trewern@hotmail.com> >CC: pgsql-odbc@postgresql.org >Subject: Re: [ODBC] Access 97 and pgsqlodbc version 7.03.0100 >Date: Wed, 21 May 2003 10:58:26 +0900 > >Ben Trewern wrote: > > > > This seems to have fixed the GPF problem but now if I look at a Master - > > Detail form I get #Deleted in some of the fields in the detail subform: > > > > Field1 Field2 Descripton1 Field4 Field5 > > >---------------------------------------------------------------------------------- > > 10 1/1/03 Description OK 1000.00 1.148 > > #Deleted #Deleted Description OK #Deleted #Deleted > > #Deleted #Deleted Description OK #Deleted #Deleted > > > > I'm not sure if the above will look OK on your e-mail client but it is >meant > > to show the first line OK but the following lines have #Deleted >everywhere > > except the Description1 field which is a memo. > >Do you create an unique index on the table or specify a >really unique identifier for the table ? > >regards, >Hiroshi Inoue > http://www.geocities.jp/inocchichichi/psqlodbc/ > >---------------------------(end of broadcast)--------------------------- >TIP 5: Have you checked our extensive FAQ? > >http://www.postgresql.org/docs/faqs/FAQ.html _________________________________________________________________ Get Hotmail on your mobile phone http://www.msn.co.uk/msnmobile
Yes there is a unique index on the master table's primary key, and there is also an index on the detail table's foreign key. Regards, Ben >From: Hiroshi Inoue <Inoue@tpf.co.jp> >To: Ben Trewern <ben_trewern@hotmail.com> >CC: pgsql-odbc@postgresql.org >Subject: Re: [ODBC] Access 97 and pgsqlodbc version 7.03.0100 >Date: Wed, 21 May 2003 10:58:26 +0900 > >Ben Trewern wrote: > > > > This seems to have fixed the GPF problem but now if I look at a Master - > > Detail form I get #Deleted in some of the fields in the detail subform: > > > > Field1 Field2 Descripton1 Field4 Field5 > > >---------------------------------------------------------------------------------- > > 10 1/1/03 Description OK 1000.00 1.148 > > #Deleted #Deleted Description OK #Deleted #Deleted > > #Deleted #Deleted Description OK #Deleted #Deleted > > > > I'm not sure if the above will look OK on your e-mail client but it is >meant > > to show the first line OK but the following lines have #Deleted >everywhere > > except the Description1 field which is a memo. > >Do you create an unique index on the table or specify a >really unique identifier for the table ? > >regards, >Hiroshi Inoue > http://www.geocities.jp/inocchichichi/psqlodbc/ > >---------------------------(end of broadcast)--------------------------- >TIP 5: Have you checked our extensive FAQ? > >http://www.postgresql.org/docs/faqs/FAQ.html _________________________________________________________________ Find a cheaper internet access deal - choose one to suit you. http://www.msn.co.uk/internetaccess
Ben Trewern wrote: > > Yes there is a unique index on the master table's primary key, and there is > also an index on the detail table's foreign key. Probably the detail table should have its primary key also or you should specify a combination of columns which could identify the detail table's row when linking the table. regards, Hiroshi Inoue