Change in file location

[#1]

Hi,

i have developed an qlickview application. The source is an excel file stored in D drive of my system.

i have sent the application and excel to other sytem . unfortunatly that system does not have D drive and hence giving an error while loading the data in application.

What is the way to get data?

Regards,

Macwan James.

[Anonymous]

Hi Macwan,

Just use a relative path (..\Folder\file.xls) to the Excel file instead of the absolute path (D:\Folder\file.xls)

[#3]

Hi,

where can i change this path in my qlikview application?

Regards,

Macwan James.

[#4]

Hi...

can u  tell me, how did u write script to transfer the file from one system to another system?

Regards,

Kabilan K.

[#5]

Add in the path for that system

for instance:

Load *

From  \\systemName\folder\excel.xls;

[erichshiino]

That path will probably be in your load statements after the 'from' as presented by Brianm10.

I consider this to be a best practice. I use a variable to point to the folder where my files are. Then I use the variable as a part of my path.

For instance:

FilePath = 'C:\Files';

Sales:

Load * from

$(FilePath)\Sales.xls ...

Then, in any qvw there would be only or two variables to set to point the QVWs to the right folders

Hope this helps,

Erich

[johnw]

In a typical application, I use DIRECTORY to specify the relative address of the directory where we keep most of our QVDs.  Files typically come from our network, and we use a network address rather than a drive letter.  So for example:

DIRECTORY ../../Server/MasterData/QVD;

LOAD ...
FROM Customer.qvd (QVD)

LOAD ...
FROM [\\someserver\somedirectory\somefile.xls]

[erichshiino]

Hi, John

Directory is very useful.

I frequently use variables to control source and destination folders.

Using a 3-tier QVD data architecture, it would be possible to have an extractor using source files and storing QVDs ( and a similar approach to a transformation layer)

In this case, I'd use a FilePath and a QvdPath

It is also possible to use directory in the beggining point to the source folder and then, at the end, use directory again to point it the store statements to the destination folder.

When you use variables, you can have all of them in the first tab of your scripts and even read data from many servers

We could use many variables in this case.

FilePath1 = '\\server'\FolderA\';

FilePath1 = ''\\server2\FolderB\';

QVDPath1 = 'C:\QVDs\' ;

[johnw]

Your use of variables sounds like a good one.