topic Re: HELP in QlikView

HELP

farolito20 — Wed, 12 Dec 2012 14:25:29 GMT

is it really necessary have a history table to trace back everything?

Re: HELP

Anonymous — Wed, 12 Dec 2012 21:25:20 GMT

Doesn't look like a QV question.

Anyway, if you want to know what happened last week or last year, it should be stored somewhere.

Regards,

Michael

Re: HELP

farolito20 — Wed, 12 Dec 2012 22:48:35 GMT

I have another question.

How I can save the modified data in a table .qvd?

For example, I have an employees_info table and I modified a phone number, but I wanna keep the other number because probably it's ussefull to make an report using old data.

id_employee , name, phone

001, carlos, 4556122

id_employee , name, phone

001, carlos, 9856741

Re: HELP

Anonymous — Thu, 13 Dec 2012 14:35:40 GMT

I would keep both old record and new record in the QVD, and add one more field - date of phone change.

Regards,

Michael

Re: HELP

farolito20 — Thu, 13 Dec 2012 14:57:48 GMT

But how?

Do you have the script?

I have this and don't work. I attached the error window

Let ThisExecTime = ReloadTime();

QV_Table:

LOAD BusinessEntityID,

ModifiedDate,

PasswordHash,

PasswordSalt,

rowguid;

SQL SELECT BusinessEntityID,

ModifiedDate,

PasswordHash,

PasswordSalt,

rowguid

FROM AdventureWorks2008.Person.Password

WHERE ModifiedDate >= #$(LastExecTime)#;

Concatenate LOAD BusinessEntityID,

ModifiedDate,

PasswordHash,

PasswordSalt,

rowguid FROM File.qvd (qvd);

STORE QV_Table INTO QV_Table.qvd (qvd);

Let LastExecTime = ThisExecTime;

Re: HELP

Anonymous — Thu, 13 Dec 2012 15:05:35 GMT

Not sure why you use #$(LastExecTime)#. Try to replace # with the singe quotes (assuming it is SQL Server database):

WHERE ModifiedDate >= '$(LastExecTime)';

Regards,

Michael

Re: HELP

farolito20 — Thu, 13 Dec 2012 15:11:32 GMT

Now, I have this error

Re: HELP

flipside — Thu, 13 Dec 2012 15:40:05 GMT

In your script, you will probably have the TimeStampFormat set, and this controls the date and time format of ReloadTime(). The error message you now see is being generated by SQL Server - it cannot understand this format, so you need to re-format the submitted string so SQL can understand it.

flipside