Large Script tab lagging

[#1]

I have a script tab that I have added a large amount of long formulas to. It equals about 75 pages when copied into a word document,

I have noticed sever lag and process time when trying to edit anything on this tab.

Does anyone know of a way to increase the memory that the script needs when working on it? It is becoming a huge pain to work on, and still have a lot of troubleshooting and edits to do to it.

It currently takes about 4 seconds from clicking on a word for it to be highlighted.

[Anonymous]

Marc,

Can you try to break this script tab in 50 or 100 smaller tabs?

Regards,

Michael

[#3]

All of these formulas are based off of a single resident loaded table. I thought Qlikview did not like to break single table loads up across scripts.

[Anonymous]

Wow, quite a load!

I just tried - QV doesn't care, just don't break it in the middle of a field name 🙂

[marcus_sommer]

I assume there are a lot of redundant code - this could be write more compact through (include)-variables and loops and will improve beside the editor-speed the maintaining, perhaps also the load-execution.

- Marcus

[fernando_tonial]

Hi, You can put your script in txt file.

In script QlikView use the command include.

Ex.

$(Include=Script.txt);

For edit the script, in editor script File > Open External Script File...

Best Regards.

Tonial.

[Anonymous]

Yes, keeping script in a separate file should be helpful by itself.

[#8]

I just tried this and while it does allow it when the script is reloading, if does not really recognize it for the syntax checker so all of the formulas are underlined with red and it does not allow me to use the smart function that changes the word color based on the function or field name, or lists functions based on what I type. This would cause editing be become faster based on performance but much slower due to always having to check if i did something right

[#9]

You are right there is probably a lot of redundant code, many formulas are referencing parts of other formulas. The code now is so complicated that I think finding and removing redundancies would take more work than dealing with the performance issue.

[#10]

I would do this, but then I do not have access to the smart scripting functions that show where the other side of a parenthesis is, or suggested functions, or field colors.