Attaching views to access.

From: Tim Uckun <tim(at)diligence(dot)com>
To: pgsql-interfaces(at)postgresql(dot)org
Subject: Attaching views to access.
Date: 2000-10-31 00:28:03
Message-ID: 4.2.0.58.20001030172047.00a4e260@mail.diligence.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-interfaces

I have two simple tables with int3 and varchar fields. I created a view
linking the two tables one to one (one is just a lookup) and attached them
to access. When I attempt to view the data I get a dialog box saying odbc
call failed and all the fields values show up as "#Name?".

Here is the end of the odbc log file..

STATEMENT ERROR: func=SC_execute, desc='', errnum=1, errmsg='Error while
executing the query'
------------------------------------------------------------
hdbc=157757728, stmt=157764064, result=0
manual_result=0, prepare=1, internal=0
bindings=0, bindings_allocated=0
parameters=157523200, parameters_allocated=10
statement_type=0, statement='SELECT
"keyfield","courtid","docketnumber","courtdivision","arrestdate","filedate",
"charge1","charge2","charge3","charge4","charge5","charge6","warrantstatus",
"filingmanner","trialtype","counseltype","dispcharge1","dispcharge2","dispch
arge3","dispcharge4","dispcharge5","dispcharge6","finelevied","restitution",
"offendertype","lisencesusp","publicservhrs","dispdate","probparole","timeto
serve","transfertodcp","childsexoff","vicunder18","race","sex","dobyear","do
bmonth","dobday","deflastname","deffirstname","defmiddlename","defattorney",
"arresttracknum","stateidnum","socsecnum","driverslicnum","description","xmi
n" FROM "qry_ar" WHERE "keyfield" = ? OR "keyfield" = ? OR "keyfield" = ?
OR "keyfield" = ? OR "keyfield" = ? OR "keyfield" = ? OR "keyfield" = ? OR
"keyfield" = ? OR "keyfield" = ? OR "keyfield" = ?'
stmt_with_params='declare SQL_CUR096749E0 cursor for
SELECT
"keyfield","courtid","docketnumber","courtdivision","arrestdate","filedate",
"charge1","charge2","charge3","charge4","charge5","charge6","warrantstatus",
"filingmanner","trialtype","counseltype","dispcharge1","dispcharge2","dispch
arge3","dispcharge4","dispcharge5","dispcharge6","finelevied","restitution",
"offendertype","lisencesusp","publicservhrs","dispdate","probparole","timeto
serve","transfertodcp","childsexoff","vicunder18","race","sex","dobyear","do
bmonth","dobday","deflastname","deffirstname","defmiddlename","defattorney",
"arresttracknum","stateidnum","socsecnum","driverslicnum","description","xmi
n" FROM "qry_ar" WHERE "keyfield" = 2 OR "keyfield" = 4 OR "keyfield" = 8
OR "keyfield" = 16 OR "keyfield" = 32 OR "keyfield" = 64 OR "keyfield" =
128 OR "keyfield" = 256 OR "keyfield" = 512 OR "keyfield" = 1024'
data_at_exec=-1, current_exec_param=-1, put_data=0
currTuple=-1, current_col=-1, lobj_fd=-1
maxRows=0, rowset_size=1, keyset_size=0, cursor_type=0,
scroll_concurrency=1
cursor_name='SQL_CUR096749E0'
----------------QResult Info -------------------------------
CONN ERROR: func=SC_execute, desc='', errnum=110, errmsg='ERROR: system
column xmin not available - qry_ar is a view'
------------------------------------------------------------
henv=157490960, conn=157757728, status=1, num_stmts=16
sock=157491896, stmts=157686056, lobj_type=-999
---------------- Socket Info -------------------------------
socket=652, reverse=0, errornumber=0, errormsg='(null)'
buffer_in=157886608, buffer_out=157890712
buffer_filled_in=3, buffer_filled_out=0, buffer_read_in=2
conn=157497328, query='close SQL_CUR09663050'
conn=157497328, query='END'
conn=157757728, query='BEGIN'
conn=157757728, query='declare SQL_CUR096749E0 cursor for SELECT
"qry_ar"."keyfield" FROM "qry_ar" '
conn=157757728, query='fetch 100 in SQL_CUR096749E0'
[ fetched 100 rows ]
conn=157757728, query='fetch 100 in SQL_CUR096749E0'
[ fetched 100 rows ]
conn=157757728, query='fetch 100 in SQL_CUR096749E0'
[ fetched 100 rows ]
conn=157497328, query='BEGIN'
conn=157497328, query='declare SQL_CUR096948A0 cursor for SELECT
"keyfield","courtid","docketnumber","courtdivision","arrestdate","filedate",
"charge1","charge2","charge3","charge4","charge5","charge6","warrantstatus",
"filingmanner","trialtype","counseltype","dispcharge1","dispcharge2","dispch
arge3","dispcharge4","dispcharge5","dispcharge6","finelevied","restitution",
"offendertype","lisencesusp","publicservhrs","dispdate","probparole","timeto
serve","transfertodcp","childsexoff","vicunder18","race","sex","dobyear","do
bmonth","dobday","deflastname","deffirstname","defmiddlename","defattorney",
"arresttracknum","stateidnum","socsecnum","driverslicnum","description","xmi
n" FROM "qry_ar" WHERE "keyfield" = 2 OR "keyfield" = 4 OR "keyfield" = 8
OR "keyfield" = 16 OR "keyfield" = 32 OR "keyfield" = 64 OR "keyfield" =
128 OR "keyfield" = 256 OR "keyfield" = 512 OR "keyfield" = 1024'
ERROR from backend during send_query: 'ERROR: system column xmin not
available - qry_ar is a view'
conn=157497328, query='ABORT'
STATEMENT ERROR: func=SC_execute, desc='', errnum=1, errmsg='Error while
executing the query'
------------------------------------------------------------
hdbc=157497328, stmt=157894816, result=0
manual_result=0, prepare=1, internal=0
bindings=0, bindings_allocated=0
parameters=157523200, parameters_allocated=10
statement_type=0, statement='SELECT
"keyfield","courtid","docketnumber","courtdivision","arrestdate","filedate",
"charge1","charge2","charge3","charge4","charge5","charge6","warrantstatus",
"filingmanner","trialtype","counseltype","dispcharge1","dispcharge2","dispch
arge3","dispcharge4","dispcharge5","dispcharge6","finelevied","restitution",
"offendertype","lisencesusp","publicservhrs","dispdate","probparole","timeto
serve","transfertodcp","childsexoff","vicunder18","race","sex","dobyear","do
bmonth","dobday","deflastname","deffirstname","defmiddlename","defattorney",
"arresttracknum","stateidnum","socsecnum","driverslicnum","description","xmi
n" FROM "qry_ar" WHERE "keyfield" = ? OR "keyfield" = ? OR "keyfield" = ?
OR "keyfield" = ? OR "keyfield" = ? OR "keyfield" = ? OR "keyfield" = ? OR
"keyfield" = ? OR "keyfield" = ? OR "keyfield" = ?'
stmt_with_params='declare SQL_CUR096948A0 cursor for
SELECT
"keyfield","courtid","docketnumber","courtdivision","arrestdate","filedate",
"charge1","charge2","charge3","charge4","charge5","charge6","warrantstatus",
"filingmanner","trialtype","counseltype","dispcharge1","dispcharge2","dispch
arge3","dispcharge4","dispcharge5","dispcharge6","finelevied","restitution",
"offendertype","lisencesusp","publicservhrs","dispdate","probparole","timeto
serve","transfertodcp","childsexoff","vicunder18","race","sex","dobyear","do
bmonth","dobday","deflastname","deffirstname","defmiddlename","defattorney",
"arresttracknum","stateidnum","socsecnum","driverslicnum","description","xmi
n" FROM "qry_ar" WHERE "keyfield" = 2 OR "keyfield" = 4 OR "keyfield" = 8
OR "keyfield" = 16 OR "keyfield" = 32 OR "keyfield" = 64 OR "keyfield" =
128 OR "keyfield" = 256 OR "keyfield" = 512 OR "keyfield" = 1024'
data_at_exec=-1, current_exec_param=-1, put_data=0
currTuple=-1, current_col=-1, lobj_fd=-1
maxRows=0, rowset_size=1, keyset_size=0, cursor_type=0,
scroll_concurrency=1
cursor_name='SQL_CUR096948A0'
----------------QResult Info -------------------------------
CONN ERROR: func=SC_execute, desc='', errnum=110, errmsg='ERROR: system
column xmin not available - qry_ar is a view'
------------------------------------------------------------
henv=157490960, conn=157497328, status=1, num_stmts=16
sock=157490976, stmts=157491024, lobj_type=-999
---------------- Socket Info -------------------------------
socket=624, reverse=0, errornumber=0, errormsg='(null)'
buffer_in=157503664, buffer_out=157507768
buffer_filled_in=3, buffer_filled_out=0, buffer_read_in=2
conn=157757728, query='close SQL_CUR096749E0'
conn=157757728, query='END'

:wq
Tim Uckun
Due Diligence Inc. http://www.diligence.com/ Americas Background
Investigation Expert.
If your company isn't doing background checks, maybe you haven't considered
the risks of a bad hire.

Browse pgsql-interfaces by date

  From Date Subject
Next Message Tom Samplonius 2000-10-31 04:36:34 Re: confused about *nix ODBC drivers
Previous Message Joseph Shraibman 2000-10-30 22:13:59 Re: JDBC- No suitable driver error