In case you get an empty view when selecting your downloaded file in CSV Touch, please try going to the same address used for downloading the file using Safari. If your file is uploaded correctly to the server, Safari should show it as a regular text file. If not, there’s something wrong with the address or the access rights for the file.
If access to your file is password-protected you might still be able to get it, depending on how the password-protection works. To supply username + password, input http://username:firstname.lastname@example.org/yourfile.csv as the address. Note that supplying username and password like this is not very secure; someone tapping into the network can pick up the username and password, so use this option with care.
You can also have a link on your homepage which when clicked will import the linked file into CSV Touch; see here for more info.
Reading the downloaded file
In general, if there seems to be problems reading the downloaded file, check the description of acceptable CSV files.
Check app setting Separator. If this is Auto, CSV Touch tries to auto-detect what character is used to separate the fields in your file. Normally for CSV files this is comma (“,”), but other characters are possible. However, this auto-detect sometimes fails to properly find the separator. In that case, please switch off the setting and select the correct separator under the Manual Separator.
After downloading your file, if you get a warning about not being able to read the file, check the encoding selected. If your file contains non-Latin characters, like Japanese or Greek, UTF8 is the likely encoding. However, depending on the application you use to create your text file, they may be encoded with Latin1 (mainly for PC files) or Mac (mainly for Mac files).
If you get a warning about different numbers of objects in different rows, the most common reason is that the address you input to your file was wrong / the file was not accessible. This will result in the web server sending back a page with html code which essentially says “Sorry, no such file exists”. CSV Touch can’t always auto-detect that this has happened; it requested a file and got a file back… To check if this is the case, try going to the address using Safari, as described above.
If everything seems fine except that some characters look wrong, like seeing “L√§ngd” instead of “Längd”, try different encodings once again (in this case the correct encoding is UTF8, but Latin1 had been selected).