RE: [INTERFACES] Foreign Keys - Mailing list pgsql-interfaces

I will fix the permission denied problem by granting access to these tables
to the Admin user.  I don't think this is the real cause of my problem.  The
null issue is the real problem  Considering your response, does this mean I
am the first user to encounter this issue?  I am not very satisfied with
Access97 and intend to replace it very soon. I am planning to port the back
end to PostgreSQL and the front end to TCL/TK in the near future.  I am
concerned about creating reports with TCL/TK and how they will interact with
a printer on Windows 95.  Access97 automatically handles a lot of things
that I will have to implement in TCL/TK.  Printing is one of them. What are
other users of PostgreSQL using for a front end?  The front end tool must
run on Windows 95.  My current Access97 database application has 9 users
that have Windows 95 workstations.

I would like to make available tools/instructions for upgrading from
Access97 to PostgreSQL (back end) and from Access97 to TCL/TK (front end).
This will take some time to implement all the details.  I will start this
process if others would like to contribute their experiences and work
arounds.

Could this problem be fixed in the ODBC driver of does it need to be fixed
in PostgreSQL?  None of the commercial databases that I have used (including
Oracle) support the syntax you are suggesting.  I wonder how this works with
SQL Server?

    -----Original Message-----
    From:    Byron Nikolaidis [SMTP:byronn@insightdist.com]
    Sent:    Tuesday, March 02, 1999 3:11 PM
    To:    Michael Davis
    Cc:    'pgsql-interfaces@postgreSQL.org'; David Hartwig
    Subject:    Re: [INTERFACES] Foreign Keys



    Michael Davis wrote:

    > Here is the psqlodbc.log file.  The first time the form opens, it
correctly
    > opens the first rentalorder.  I immediately moved to the new
record in
    > Access which opens a message box with an ODBC error (no
description).  I the
    > blank rental order looks okay but the rental order lines records
all have
    > errors.  Even if I move back to a valid record, the order lines
will show
    > only errors.
    >

    Here's what I see.  The first problems are the permission denied
errors.   It may be due to the
    uid=admin.  You could probably set the uid to something more
reasonable in your connect string
    in Access.


    conn=153944104, query='SELECT "logvalues"."id" FROM "logvalues" '
    ERROR from backend during send_query: 'ERROR:  logvalues: Permission
denied.'

    conn=153944104, query='SELECT "memberid" ,"firstname" ,"lastname"
FROM "membership" ORDER BY
    "lastname" ,"firstname"  '
    ERROR from backend during send_query: 'ERROR:  membership:
Permission denied.'

    conn=153944104, query='SELECT "memberid" ,"firstname"
,"middleinitial" ,"lastname" ,"surname"
    ,"birthdate" ,"statusid" ,"accountbalance" ,"duesbalance"
,"seminarbalance" ,"selected"
    ,"otheritemsdiscoursesplusone" ,"originalcontactid" ,"gender"
,"email" ,"optname"
    ,"recordtype"  FROM "membership" '
    ERROR from backend during send_query: 'ERROR:  membership:
Permission denied.'

    conn=153944104, query='SELECT "membership"."memberid"
,"membership"."firstname"
    ,"membership"."lastname" ,"memberservices"."serviceid"  FROM
"memberservices","membership"
    WHERE (("memberservices"."serviceid" IN (8 ,12 ) ) AND
("membership"."memberid" =
    "memberservices"."memberid" ) ) ORDER BY "membership"."lastname"
,"membership"."firstname"  '
    ERROR from backend during send_query: 'ERROR:  memberservices:
Permission denied.'

    conn=153944104,

SQLDriverConnect(out)='DSN=PostgreSQL;DATABASE=mp;SERVER=192.168.97.2;PORT=5
432;UID=Admin;PWD=;READONLY=0;PROTOCOL=6.4;FAKEOIDINDEX=0;SHOWOIDCOLUMN=0;RO
WVERSIONING=0;SHOWSYSTEMTABLES=1;CONNSETTINGS='

    conn=153944104, query='SELECT "memberid" ,"firstname"
,"middleinitial" ,"lastname" ,"surname"
    ,"birthdate" ,"statusid" ,"accountbalance" ,"duesbalance"
,"seminarbalance" ,"selected"
    ,"otheritemsdiscoursesplusone" ,"originalcontactid" ,"gender"
,"email" ,"optname"
    ,"recordtype"  FROM "membership" '
    ERROR from backend during send_query: 'ERROR:  membership:
Permission denied.'
    STATEMENT ERROR: func=SC_execute, desc='', errnum=1, errmsg='Error
while executing the query'



    The second problem is this:

    conn=153237224, query='SELECT "RentalOrders"."rentalorderlinesid"
FROM "rentalorderlines"
    "RentalOrders" WHERE ("rentalorderid" =  NULL ) '
    ERROR from backend during send_query: 'ERROR:  parser: parse error
at or near "null"'
    STATEMENT ERROR: func=SC_execute, desc='', errnum=1, errmsg='Error
while executing the query'


    Since postgres will not recognize the syntax (where 'col' = null)...
it only recognizes
    "isnull".  I was hoping someone would have added the ability for the
parser to handle this at
    some point (Hey Dave, maybe you could contribute something here man
:-).


    Byron