topic Re: Preceding load OleDB failed in QlikView

Preceding load OleDB failed

terezagr — Thu, 05 Mar 2015 16:27:45 GMT

Hi all,

I am trying to perform preceding load:

Oledb connection string

Table1:

Load *,

Hour(snapshot) as Hour,

Year(snapshot) as Year;

SQL Select

from snapshot;

Store Table1 into snapshot.qvd;

I keep getting the following:

1. When the script is like this, with star Load *, I get OLEDB failed:

Table1:

Load *,

Hour(snapshot) as Hour,

Year(snapshot) as Year;

SQL Select

from snapshot;

Store Table1 into snapshot.qvd;

2. When the script is like this, without the star, I get only data for Hour and Year and not all from snapshot table

Table1:

Load

Hour(snapshot) as Hour,

Year(snapshot) as Year;

SQL Select

from snapshot;

Store Table1 into snapshot.qvd;

All help appreciated

Re: Preceding load OleDB failed

Colin-Albert — Thu, 05 Mar 2015 16:33:22 GMT

Is there another field names Hour or Year so you are getting duplicate fields?

Have you tried the load replacing * with the list of fields?

Re: Preceding load OleDB failed

terezagr — Thu, 05 Mar 2015 16:43:24 GMT

There is no other field called Hour or Year. Although there are some data transformation in the SQL bit

e.d. CODE AS TARGET_CODE

Re: Preceding load OleDB failed

terezagr — Thu, 05 Mar 2015 17:35:47 GMT

It looks like it load only fields specified in Load script.

That's why I want to use the *…but with no luck

Re: Preceding load OleDB failed

Thu, 05 Mar 2015 17:45:22 GMT

Hi,

Can you upload the structure(all Columns name) of the snapshot table.

Regards

Nandkishor Pandirkar

Re: Preceding load OleDB failed

terezagr — Thu, 05 Mar 2015 18:47:43 GMT

Sorry, I think I will not be able to do that

Anyway, the SQL loads data from 3 different tables and does a basic transformation in the script too…like renaming fields, decoding fields etc.

Colin asked me to load all the fields instead of star *…should I load the original names, or the renamed fields' names?

Re: Preceding load OleDB failed

Ralf-Narfeldt — Fri, 06 Mar 2015 09:19:37 GMT

If you are doing AS transformations in the SQL SELECT part, these are not always supported. It is dependent on the OLEDB provider as it is done on that side.

If possible you can move all renaming and transformations to the preceding LOAD.

Re: Preceding load OleDB failed

terezagr — Tue, 10 Mar 2015 14:50:03 GMT

I have solved this by:

1. SQL load of table Table1

2. Load of my logic and all fields Resident Table 1