If I have a file called "C:\test.txt" and the files consists of the
following:

------
Goodbye
Hello
Next Year
------

How you would open that file and export only the "Hello" string to a new
file which is say "C:\output.txt"

I am sure it is something easy that I am just overlooking but I am trying to
design a log analyzer program and I can't seem to get started.

If the log analyzer is for your use only, consider using Perl.  Really.
Perl excels at text parsing, and with the correct invocation the code to do
what you need reduces to:

print if /Hello/;

Rick

Try the following. A bit old fashioned but it should work.

Open "c:\test.txt" For Input As #1
Open "c:\output.txt" for Ouput as #2
100 If EOF(1) Then GoTo 300
Input #1, e
if e = "Hello" then goto 200 else goto 100
200 Print #2, e
goto 100: rem just in case there is more than one hello
300 Close

Hugh McKerrell

On Sat, 30 Dec 2000 03:30:16 GMT, "Kevin Wells"

Sorry to shout, but GoTos are the WORST possible thing to use when you are
trying to write structured code, because they make program flow entirely
unpredictable.

If you must use Visual Basic for this task, then do it this way  -

dim sIn as string
dim sOut as string
dim sTest as string

sIn = "c:\test.txt"
sOut = "c:\output.txt"

open sIn for Input as #1
  open sOut for Output as #2
    do while not eof(1)
      sTest = Line Input #1

      if sTest like "hello" then
        print #2, sTest
      end if

      DoEvents
    loop
  close #2
close #1

This, I am sure you will agree, is FAR more elegant and FAR more predictable
in its effects; it also has the advantage of being clear and easy to read.

Here is a question for you.  If you take the same example but had a text
file like the following:

User Logged on at: 11:24
User Transferred 10 Files
User Logged off at 11:36
User Logged on at 12:45
User Logged off at 01:45

Using the below example as a reference, is there anyway to isolate only the
"User Logged on at: ??:??" lines to the output file?  I have tried using the
filter function to no avail as it keeps giving me the "Type Mismatch" error
when using the following code:

-------------------
Private Sub Command2_Click()
Dim str As String
Dim search As String

Open "c:\test.log" For Input As #1
Open "c:\textfinish.log" For Output As #2
search = "FTP"
Do Until EOF(1)
    Line Input #1, str
    If Filter(str, search) Then
        Print #2, str
    End If
Loop
--------------------

If anyone else knows the answer then please share.

Thanks

The function that you need to use in your case is the VB Instr function.
This searches a string to see if a specified substring exists within it. Try
the following:

Private Sub Command1_Click()
Dim str As String
Dim search As String
Open "c:\test.log" For Input As #1
Open "c:\textfinish.log" For Output As #2
search = "User logged on"
Do Until EOF(1)
 Line Input #1, str
 If InStr(1, str, search, vbTextCompare) > 0 Then
  Print #2, str
 End If
Loop
Close 1
Close 2
End Sub

Mike

I'm playing with VB.NET at the moment... Try, Catch, Throw... mmm exception
handling makes VB programming a LOT nicer, and obviates the need for gotos.

So, if you replaced this :
      If Filter(str, search) Then
with
      If search like str then

it would work well.

you would also have to change the 'search' variable to me something like
'user logged on at*' in order that it matched all lines like that.

HTH

Spend some time studying the help files until you understand each
of the File I/O statements used below:

Dim iFb1 As Integer, iFB2 As Integer, sTmp As String

iFB = FreeFile
Open "C:\Test.txt" For Input As #iFB

Do While Not EOF(iFB)
  Line Input #1, sTmp
  if sTmp = "Hello" Then   'Or: If Instr(sTmp, "Hello")  if you prefer.
     Open "C:\Output.txt" For Output As iFB2
     Print #iFB2, sTmp
     Close iFB2
     Exit Do
  End if
Loop
Close iFB1
-------------------------

I'm glad that Visual Basic is soon about to catch up with the twenty year
old Commodore Amiga ;-)

I really find your kind of code as strange as I am sure you find mine.
There are no rules for doing this kind of thing and if it works, why
fix it? How on earth there can be a right and a wrong way of using vb
I totally fail to see. If it works, it works.

I have written basic code long before vb appeared so gotos are
entirely routine to me. I can honestly say I never get confused with
them and for the life of me I cannot see why you should get so het up.
One detail I note, my code size is about half yours. Does that not
tell you something? Like pedantic for the sake of it?

Anyway, I have no intention of getting involved in any dispute. But I
just thought I should respond to rather totally reject your
suggestions. I wont complain about your kind of thing if you dont
complain about mine.

Hugh McKerrell

On Sat, 30 Dec 2000 13:17:24 -0000, "Michael Williams"

Mike