Trouble with input field

[#1]

Hi,

I'm playing around with input fields and have hit a problem, not one i've seen before, can anyone help.

I'm loading a simple table, with one field 'Comment' as an input field. I then create an table box, all seems well and then try to edit the comment field, but this happens?! Anyone come accross this before? Can someone help. Many Thanks.... Matt

Here's the code:

Comments:

INPUTFIELDComment;

LOAD

MonthName(Month) AS Month,

Meeting,

KPI,

Comment;

Month&Meeting&KPI AS Key,

SQL

SELECT SELECT

MonthName(Month) AS Month,

Meeting,

KPI,

Comment;

Month&Meeting&KPI AS Key,

SQL

SELECT SELECT MonthName(Month) AS Month,

Meeting,

KPI,

Comment;

Month&Meeting&KPI AS Key,

SQL

SELECT SELECT

Comment,

DateTime,

KPI,

Meeting,

Month,

UserID

FROMCorporateMI.dbo.Comments;

[#2]

I've changed the code to this and seems to have fixed it. Would be interested to know why if anyone has any ideas. Didn't seem to like me editing the NULL values when loaded directly.

Comments:

INPUTFIELD Comment;

LOAD MonthName(Month) AS Month,
Meeting,
KPI,
Month&Meeting&KPI AS Key,
IF(LEN(Comment) >0, Comment,' ') AS Comment;

SQL SELECT Comment,
DateTime,
KPI,
Meeting,
Month,
UserID
FROM CorporateMI.dbo.Comments;

[pover · Accepted solution]

We would have to confirm this with somebody from QlikTech, but an inputfield appears to leave a space in RAM for every value in a column whether it is unique or not. (Normally, QlikView would "compress" the non-unique values and that is the reason many inputfield can drastically increase file size.) However, when a value is null, QlikView doesn't seem to leave a space in RAM for that value to be changed.

Also, avoid using inputfield in pivot tables because in a pivot table you will see missing values and you will confront the same error when you try to change it because QlikView doesn't leave a space in RAM to change a missing value.

I hope that makes sense.

[#4]

Yep, makes sense to me. So the answer seems to be to set it to '', not NULL... i guess qlikview must treat these differently

thanks Karl