Question: "File Already Open" Error

[DarkOne]

I continued my debugging this morning and found the problem. There was actually a problem in my SaveFilters procedure in which I was referring to a non-existent object. I have resolved this problem by ensuring that these objects are loaded.

I appreciate your help o.OV and everyone else to tried to help!

[Stealth]

"While Not" should be changed to "Until"

My CS teacher disagrees. He considers "While Not" better form. Perhaps from his background in C/C++?

[Newby]

I use Loop until EOF(1) -_-

[Grok]

Code Select Expand

Do While EOF(FileNum) = False    'or NOT EOF(FileNum)
  '
Loop

That is the form I always use for reading files in VB.  Even when using Scripting.TextStream object.

Code Select Expand

Set TS = fso.OpenTextStream(...)
Do While TS.AtEndOfStream = False
   '
Loop

[DarkOne]

Is there any advantage of using one over the other, other than typing less characters? Just a matter of preference?

[Imperceptus]

Now would be an excellent opportunity for you to Sharpen up on how to debug a program.  Step Into, Step over, variable/expression/control watches and so forth.

[o.OV]

I continued my debugging this morning and found the problem. There was actually a problem in my SaveFilters procedure in which I was referring to a non-existent object. I have resolved this problem by ensuring that these objects are loaded.

I appreciate your help o.OV and everyone else to tried to help!

oh.. strange.
I don't understand object oriented programming very well.
How did a non-existent object cause a file to remain open?

[o.OV]

"While Not" should be changed to "Until"

My CS teacher disagrees. He considers "While Not" better form. Perhaps from his background in C/C++?

I did try testing this.

Note:
I use two different projects
because I found the arrangement of code
could actually make a difference in speed.
(slower/faster)
Can someone give an explanation as to why?

Don't forget to compile into an executable ~ !!

Do While Not

Code Select Expand



Private Declare Function GetTickCount Lib "kernel32.dll" () As Long
Dim T As Long, X As Long, XX As Long
Private Sub Form_Load()
   
   Unload Me
   
   XX = 100000000
   X = 0
   T = GetTickCount
   Do While Not X
       XX = XX - 1
       If XX = 0 Then X = -1
   Loop
   MsgBox "Do While Not " & GetTickCount - T

End Sub



and

Do Until

Code Select Expand



Private Declare Function GetTickCount Lib "kernel32.dll" () As Long
Dim T As Long, X As Long, XX As Long
Private Sub Form_Load()
   
   Unload Me
   
   XX = 100000000
   X = 0
   T = GetTickCount
   Do Until X
       XX = XX - 1
       If XX = 0 Then X = -1
   Loop
   MsgBox "Do Until " & GetTickCount - T

End Sub



[DarkOne]

I continued my debugging this morning and found the problem. There was actually a problem in my SaveFilters procedure in which I was referring to a non-existent object. I have resolved this problem by ensuring that these objects are loaded.

I appreciate your help o.OV and everyone else to tried to help!

oh.. strange.
I don't understand object oriented programming very well.
How did a non-existent object cause a file to remain open?

I referred to the object while the file was open, but I don't quite understand why it didn't prompt me about the object. Odd.

[o.OV]

I referred to the object while the file was open, but I don't quite understand why it didn't prompt me about the object. Odd.

Are you using "On Error .." ?

[DarkOne]

Nope.

If there are errors, I like to see what they are and fix them. I don't usually like to depend on "On Error Resume Next".

[SPY-3]

if you called a on error goto event where it opens the file then add Close#1 or w/e ur integer or number is