R. Vajsar wrote:
>
> I had sent vtrace in last but one mail message ("The error occures
only
> when creating a query based on VIEW: ..............").
> Well, once more....
> R.V.
>
I can see the command:
SELECT K_P_VYVOJ.ID, K_P_VYVOJ.SYSKEY FROM APT.K_P_VYVOJ K_P_VYVOJ
And as we saw in a previous mail
(CREATE VIEW K_P_VYVOJ AS SELECT ...
And as I wrote: views do not have syskey-column, why do you select this
column?
Elke
SAP Labs Berlin
> Zabach, Elke wrote:
>
> > R. Vajsar wrote:
> >
> >>Oh yes. I'm only looking for relationship between primary key,
SYSKEY
> >
> > and
> >
> >>error 4005 ("check if the table mentioned has a user-defined primary
> >
> > key
> >
> >>(then SYSKEY will NOT exist) or not"). If a view hasn't index, then
> >
> > SYSKEY
> >
> >>doesn't exist and error 4005 in this case is a feature?
> >>The primary problem is error: Column not found,-4005 POS(32) Unknown
> >>column name:SYSKEY
> >>when I want to get data from view through ODBC into MS query. Base
> >
> > table
> >
> >>of view has index.
> >>I inspect the vtrace file, but I don't see anything useful:-(
> >>R.V.
> >
> >
> > You mix things.
> >
> > An index and the existence or not-existence of an index has NOTHING
to
> > do with each other.
> >
> > A view does not have a column syskey, even if select * from
table_tab
> > and table_tab has no user-defined-key, meaning table_tab has a
column
> > named syskey.
> >
> > Why did you not send the vtrace to the list as I asked you to do if
you
> > are not able to find the problem? With your explanation, mixing up
> > things and without the statements, noone will be able to explain
what is
> > going on.
> >
