Chris,
Without seeing your code, I can't tell what's going on. KiX certainly can handle long folder and file names. The rules are no different than with Windows. Just so long as they are wrapped in quotes so that it can delineate parms. If you have nested quotes however, you need to use single quotes on the outside and double quotes on the inside. If you are trying to build strings with embedded quotes, you need to use CHR(34).

Just to be certain, Itested the following with both 4.02 and 3.62 and there was no prob.

code:

Break on
$CRLF=CHR(13)+CHR(10)
If Exist("C:\Documents and Settings\Admin\Desktop\new extra long log.txt")
  Del "C:\Documents and Settings\Admin\Desktop\new extra long log.txt"
EndIf
If Open(1,"C:\Documents and Settings\Admin\Desktop\new extra long log.txt",5) <> 0
  ? "Newlog file not opened, error code: [" + @ERROR + "]"
  GoTo skip
EndIf
If Open(2,"C:\Documents and Settings\Admin\Desktop\log.txt") = 0
  $line = ReadLine(2)
  WHILE @ERROR = 0
    ? "Line read: [" + $line + "]"
    If instr($line, "20020126") <> 0
      WriteLine(1,$Line+$CRLF)
    Endif
    $line = ReadLine(2)
  LOOP
  Close (2)
ELSE
  BEEP
  ? "Log file not opened, error code: [" + @ERROR + "]"
EndIf

:skip
Close (1)
get $_

Look over your code carefully and make sure you don't have an odd number of quotes or an if without an endif etc. Download KiXStripxxx from http://home.wanadoo.nl/scripting/ and use it to check your code.

[ 28 January 2002: Message edited by: LLigetfa ]

_________________________
Give a man a fish and he will be back for more. Slap him with a fish and he will go away forever.