Skip to main content
Announcements
NEW: Seamless Public Data Sharing with Qlik's New Anonymous Access Capability: TELL ME MORE!
cancel
Showing results for 
Search instead for 
Did you mean: 
curiousfellow
Specialist
Specialist

Copied new file over old file but kept old file/script

I have a folder containing my "developing" files and a folder containing my "production" files. All  on a development server.
Today I copied a file from my "developing" folder to my "production" folder replacing an old file with the same name. When I opened the file in my "production" folder it still contained the script of the previous file with the same name in the "production" folder.

I tried several options like deleting the previous file from the "production" folder, but when I opened the newly copied file in the "production" folder it still showed the old script.

In an old thread with a similair problem I found that the cause could be that a subfolder with the name of the file and the text "-prj" added to it exists (in the "production" folder?). After renaming that folder the problem seemed to be solved.

I  have two questions: 
- Why does this *-prj folder exists ? Is it created by document-analyzer ?
- How to prevent that something like this happens, there is a risk that you don't see you are working with an old script. In my case I would copy this file to the "production-server" .

We are using Qlikview May 2021 SR1

Labels (1)
1 Solution

Accepted Solutions
marcus_sommer

By default there is no prj-folder else they must be created intentionally - which is usually done manually but some scan/backup applications/logic may also create them. It's not a mistake in any way or means a special risk else it enables some advanced features. Of course you need to know what your folders contains ... which includes also other content like shared/meta/log/pgo-files and you need to consider them, too within the development/maintaining task-chain.

View solution in original post

1 Reply
marcus_sommer

By default there is no prj-folder else they must be created intentionally - which is usually done manually but some scan/backup applications/logic may also create them. It's not a mistake in any way or means a special risk else it enables some advanced features. Of course you need to know what your folders contains ... which includes also other content like shared/meta/log/pgo-files and you need to consider them, too within the development/maintaining task-chain.