Hello,

I am using version 10.0.3807 of SQL Anywhere with VS .net
2005 C#.

I am using the ULFileTransfer object with a mobilink server
to download some files. I have the ml server setup with
-ftr C:\MyDirectory. I want to also download files from a
sub directory of C:\MyDirectory so I tried to append this to
the file name in the code "\NewFoler\AnotherFile.txt"
The server reports an error of could not find file
"\NewFolder\AnotherFile.txt". The file is located in that
sub directory.

Is what I want to do possible with one mobilink service? If
so, where did I go wrong?

Also, when this (or any error) happens, I don't get very
good error messages from the ULFileTransfer object - the
server log shows a nice error message. How do I get that
error?

Thank you in advance,
Paula

I believe mobilink only supports one -ftr parameter but MobiLink will look in two places - it first looks for the file in the C:\MyDirectory\<ml user>\ directory then in the C:\MyDirectory\ directory (assuming -ftr C:\MyDirectory). This allows you to deliver different files to different users.

From the ULFileTransfer class > FileName property doc:
FileName must not include any drive or path information, or the MobiLink server will be unable to find it. For example, "myfile.txt" is valid, but "somedir\myfile.txt", "..\myfile.txt", and "c:\myfile.txt" are all invalid.

This is for security reasons.

If you start a second MobiLink on a different port, you can work around this.

---
Philippe Bertrand
Sybase iAnywhere

<Paula> wrote

I believe mobilink only supports one -ftr parameter but MobiLink will look in two places - it first looks for the file in the C:\MyDirectory\<ml user>\ directory then in the C:\MyDirectory\ directory (assuming -ftr C:\MyDirectory). This allows you to deliver different files to different users.

From the ULFileTransfer class > FileName property doc:
FileName must not include any drive or path information, or the MobiLink server will be unable to find it. For example, "myfile.txt" is valid, but "somedir\myfile.txt", "..\myfile.txt", and "c:\myfile.txt" are all invalid.

This is for security reasons.

If you start a second MobiLink on a different port, you can work around this.

---
Philippe Bertrand
Sybase iAnywhere

<Paula> wrote

I believe mobilink only supports one -ftr parameter but MobiLink will look in two places - it first looks for the file in the C:\MyDirectory\<ml user>\ directory then in the C:\MyDirectory\ directory (assuming -ftr C:\MyDirectory). This allows you to deliver different files to different users.

From the ULFileTransfer class > FileName property doc:
FileName must not include any drive or path information, or the MobiLink server will be unable to find it. For example, "myfile.txt" is valid, but "somedir\myfile.txt", "..\myfile.txt", and "c:\myfile.txt" are all invalid.

This is for security reasons.

If you start a second MobiLink on a different port, you can work around this.

---
Philippe Bertrand
Sybase iAnywhere

<Paula> wrote

I believe mobilink only supports one -ftr parameter but MobiLink will look in two places - it first looks for the file in the C:\MyDirectory\<ml user>\ directory then in the C:\MyDirectory\ directory (assuming -ftr C:\MyDirectory). This allows you to deliver different files to different users.

From the ULFileTransfer class > FileName property doc:
FileName must not include any drive or path information, or the MobiLink server will be unable to find it. For example, "myfile.txt" is valid, but "somedir\myfile.txt", "..\myfile.txt", and "c:\myfile.txt" are all invalid.

This is for security reasons.

If you start a second MobiLink on a different port, you can work around this.

---
Philippe Bertrand
Sybase iAnywhere

<Paula> wrote

I believe mobilink only supports one -ftr parameter but MobiLink will look in two places - it first looks for the file in the C:\MyDirectory\<ml user>\ directory then in the C:\MyDirectory\ directory (assuming -ftr C:\MyDirectory). This allows you to deliver different files to different users.

From the ULFileTransfer class > FileName property doc:
FileName must not include any drive or path information, or the MobiLink server will be unable to find it. For example, "myfile.txt" is valid, but "somedir\myfile.txt", "..\myfile.txt", and "c:\myfile.txt" are all invalid.

This is for security reasons.

If you start a second MobiLink on a different port, you can work around this.

---
Philippe Bertrand
Sybase iAnywhere

<Paula> wrote

I believe mobilink only supports one -ftr parameter but MobiLink will look in two places - it first looks for the file in the C:\MyDirectory\<ml user>\ directory then in the C:\MyDirectory\ directory (assuming -ftr C:\MyDirectory). This allows you to deliver different files to different users.

From the ULFileTransfer class > FileName property doc:
FileName must not include any drive or path information, or the MobiLink server will be unable to find it. For example, "myfile.txt" is valid, but "somedir\myfile.txt", "..\myfile.txt", and "c:\myfile.txt" are all invalid.

This is for security reasons.

If you start a second MobiLink on a different port, you can work around this.

---
Philippe Bertrand
Sybase iAnywhere

<Paula> wrote

I believe mobilink only supports one -ftr parameter but MobiLink will look in two places - it first looks for the file in the C:\MyDirectory\<ml user>\ directory then in the C:\MyDirectory\ directory (assuming -ftr C:\MyDirectory). This allows you to deliver different files to different users.

From the ULFileTransfer class > FileName property doc:
FileName must not include any drive or path information, or the MobiLink server will be unable to find it. For example, "myfile.txt" is valid, but "somedir\myfile.txt", "..\myfile.txt", and "c:\myfile.txt" are all invalid.

This is for security reasons.

If you start a second MobiLink on a different port, you can work around this.

---
Philippe Bertrand
Sybase iAnywhere

<Paula> wrote

I believe mobilink only supports one -ftr parameter but MobiLink will look in two places - it first looks for the file in the C:\MyDirectory\<ml user>\ directory then in the C:\MyDirectory\ directory (assuming -ftr C:\MyDirectory). This allows you to deliver different files to different users.

From the ULFileTransfer class > FileName property doc:
FileName must not include any drive or path information, or the MobiLink server will be unable to find it. For example, "myfile.txt" is valid, but "somedir\myfile.txt", "..\myfile.txt", and "c:\myfile.txt" are all invalid.

This is for security reasons.

If you start a second MobiLink on a different port, you can work around this.

---
Philippe Bertrand
Sybase iAnywhere

<Paula> wrote

I believe mobilink only supports one -ftr parameter but MobiLink will look in two places - it first looks for the file in the C:\MyDirectory\<ml user>\ directory then in the C:\MyDirectory\ directory (assuming -ftr C:\MyDirectory). This allows you to deliver different files to different users.

From the ULFileTransfer class > FileName property doc:
FileName must not include any drive or path information, or the MobiLink server will be unable to find it. For example, "myfile.txt" is valid, but "somedir\myfile.txt", "..\myfile.txt", and "c:\myfile.txt" are all invalid.

This is for security reasons.

If you start a second MobiLink on a different port, you can work around this.

---
Philippe Bertrand
Sybase iAnywhere

<Paula> wrote