Kill Process

[sethu_r123]

Hi!
i have written a software in vb6 with Sql server 2000 as database.
the software works fine but i have few problems which i could solve.
1) when i close the application i find that the process in the task manager is still running?
how to kill the process once i exit from the software.

please help me in this regard.
its very urgent.

with regards!
Sethuraman R

[seenu_1st]

may be u didn't close the recordset, try something like this..

    If Not Rs Is Nothing Then
        'first, check if the state is open, if yes then close it
        If (Rs.State And adStateOpen) = adStateOpen Then
            Rs.Close
        End If
        'set them to nothing
        Set Rs = Nothing
    End If

then unload all forms

Dim F As Form
   For Each F In Forms
      Unload F
      Set F = Nothing 'clean up
   Next

[Siddharth Rout]

With this little information, I cannot comment much... Can you show your project for a faster resolution?

[RobDog888]

Can you place a breakpoint on your code that checks if the rs is open and if so closes it? I dont believe you need to do a bitwise comparison on it. Just check if its adStateOpen and if so, close

[si_the_geek]

You should use a bitwise comparison as seenu_1st showed, because the .State property of ADO objects can have multiple values at the same time - such as Open and Executing.


For an explanation (and example code) for how you should be closing a form/program, see the article How should I close my form/program/class? from our Classic VB FAQs (in the FAQ forum)

[RobDog888]

Then I guess Microsoft is wrong...

Note the "GetState" procedure as well as the error handler:
http://msdn.microsoft.com/en-us/libr...60(VS.85).aspx

Code Examples 1-5:
http://msdn.microsoft.com/en-us/library/ms807027.aspx

[si_the_geek]

As is often the case, Microsoft don't show every property/method to the full in their examples - and occasionally (like in this case) show things which are over simplified, and thus go against the documentation of those properties.

The actual documentation for State includes this:

The object's State property can have a combination of values. For example, if a statement is executing, this property will have a combined value of adStateOpen and adStateExecuting.

I've seen this happen myself (and it's been an issue on the forums before), so it seems that the example from Microsoft is not entirely safe - but their explanation is fine.

I guess they simplified the example so that they didn't have to explain bit masking.