PPC 6700 Sprint -- FileName Problem

PPC 6700 Sprint -- FileName Problem

• Tomay

  I am giving textBox to enter filename. When user enters 123 or 123.34 or 123_34, my program supposed to create 123.txt or 123.34.txt or 123_34.txt. But it is not happening in PPC6700. It works fine in Dell Axim X51v(this is the one I have).

  I do not have code right now. I can send that to you when I go home after work. But here is the high level logic..

  user enters filename. I take the filename and Concatenate .txt at end of it and Concatenate Predefined Directory at the Begining of it and do create Stream Writer with filepath and do WriteLine 10 - 15 times and close the file.

  The customer said he did not receive any error but file is not created. If he enters abc then abc.txt has been created. I will send you the code today evening.

  Thanks
  

  
  

• tomkle

  What sort of input control are you using to capture the filename value (no 6700 here, I work with Treo 700Ws and Cingular 2125s, but a couple friends have 6700s that I play with.)

  Can you cut and paste your code here

  
  

• DotNet_369

  Andrew,

  This is the code I am using. User enters filename and I take the filename and do the following
  

  ArrayList alist = new ArrayList(); (This arraylist contains 10 to 20 Items) and being passed for all the items to be written.

  strFileName	=	txtFilename.Text;
  string path	=	System.IO.Path.GetDirectoryName
  			( System.Reflection.Assembly.GetExecutingAssembly().GetName().CodeBase );
  	path  =    path + "\\Loan\\" + strFileName + ".txt";

  for example finalpath might be \\Program Files\\BanyanSoft\\LLSRPRO\\LOAN\\123.txt;
  
  
  
  
  
  StreamWriter sw	= new StreamWriter(path, false);
  for(int i = 0; i < aList.Count; i++)
  {

  	sw.WriteLine(alist.ToString());
  
  
  }
  sw.Flush();
  sw.Close();

  I have retyped the code. Please ignore any spelling mistakes. This is the exact logic being used. My customer reported that if the file name is 123 it is not working. No file is created and no error message in PPC6700. But it works fine in Dell Axim X51V and other PDA's.
  Can you test this code in PPC6700 and let me know..
  
  Thanks,
  Vijay
  
  

  
  

  
  

• khanhnguyen99

  Andrew,
  It works exactly as I intended in Dell Axim X51V and in the 2003SE emulators. These files directories I have specified exists in my device. The user said if he enters filename like abc it works. When he enters all numeric it does not work and no error messages.
  Can you explain what are all the name handling differences between those devices I am not using any special name handling. I use what user enters. I have the same code executing for all mobile devices. Do I have to make all uppercase
  Can you give me differences between those devices on filehandling Is there a safe way to handle(code sample) those by knowing the differences
  Thanks,
  Vijay

  
  

• jerrymei

  Any updates here
  

• Paulu

  are you certain the path exists exactly as specified on the device in deployment the file isn't ending up in the root or some other higher level folder than your intended path Is filename capitalization handled exactly the same between the devices I've noticed filesystem differences between WM5.0 on a Treo 700w and WM5.0 on an HTC Faraday when it comes to name handling.

  
  

• HOBO59458

  VijayVeera wrote:

  Andrew, It works exactly as I intended in Dell Axim X51V and in the 2003SE emulators. These files directories I have specified exists in my device. The user said if he enters filename like abc it works. When he enters all numeric it does not work and no error messages. Can you explain what are all the name handling differences between those devices I am not using any special name handling. I use what user enters. I have the same code executing for all mobile devices. Do I have to make all uppercase Can you give me differences between those devices on filehandling Is there a safe way to handle(code sample) those by knowing the differences Thanks, Vijay

  it's been a few months, but if I recall correctly, the Treo would overwrite an existing file without complaint, whereas my 2125s would not, despite the same methods and create/append parameters. if I get a chance to dig up my notes from January, I'll see if I can find more examples.

  
  
• PPC 6700 Sprint -- FileName Problem