R. Vajsar wrote: > > The error occures only when creating a query based on VIEW: > (CREATE VIEW K_P_VYVOJ AS SELECT ID, KLIENT_ID, PRODUKT, SMLOUV_TYP, ZMENA > = 1, VALUE(DATUM_OD,'1994-01-01') AS DATUM FROM KLIENT_PRODUKT UNION > SELECT ID, KLIENT_ID, PRODUKT, SMLOUV_TYP, ZMENA = -1, DATUM_VRAC AS DATUM > FROM KLIENT_PRODUKT WHERE DATUM_VRAC IS NOT NULL). > > SYSKEY not exist probably - I can't create index for this view. What am I > doing wrong? > R. V. >
Do I understand correctly that you try to do a create index for the view K_P_VYVOJ? You never can create an index for a VIEW. You only can create index for basetables, in your case KLIENT_PRODUKT (I hope, this is no view, too). Elke SAP Labs Berlin > Zabach, Elke wrote: > > > R. Vajsar wrote > > > >>Hello, > >> > >>We are using the MaxDB version 7.5.00.19. My application works well, > > > > but > > > >>when I'm using Microsoft Query to import data from view, the error > >>occures: Column not found,-4005 POS(32) Unknown column name:SYSKEY. > >> > >>Has anyone an idea, what can I do? > > > > > > As I do not know the statements sent to the kernel in this context, as I > > do not know the table being part of the statement resulting in that > > error and as I do not know if this table does have a user-defined > > primary key or not: > > You can do a vtrace according to > > http://sapdb.2scale.net/moin.cgi/VTrace, but change default in 1. > > and 6. to default order . > > The search in the resulting file for -4005, look upwards a little bit > > (to the corresponding part starting with REQUEST:), inspect the SQL, you > > will find there and then check if the table mentioned has a user-defined > > primary key (then SYSKEY will NOT exist) or not. > > > > If that will not give the idea what happens, send the table definition > > and the statement resulting in the error to the list. > -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
