Question: I query a MySql table with 5 different records.
Then I fill a VB6 Data Report.
I have 5 records in the table with fields Name and Surname, problem is the report shows
5 same names instead of five different names.

The 5 same names all belong to the last record fetched from the database, here is the code to fill the Data Report label at runtime:

```
    Set rs = New ADODB.Recordset       'Creates record set
    strSQL = "select * from person"
     rs.Open strSQL, cn, strDBCursorType, strDBLockType, strDBOptions

If rs.EOF Then
   GoTo ExitSub
Else
    For B = 1 To rs.RecordCount
   'MsgBox (rs!Name + " " + rs!Surname)
    rptRuntime.Sections("Section1").Controls("lblName").Caption = rs!Name
   rs.MoveNext
    Next B
End If
    rptRuntime.Show

```

The label that is being filled is placed in the Detail section, named "Section1".

Answer: 
Have you tried opening a terminal window and running `top`, or opening `Activity Monitor`, then running each one individually and seeing when your CPU starts to climb? Both `top` and `Activity Monitor` will let you sort by the CPU load an app is generating. Use `top -o cpu` and watch to see if the highest load is the app you ran or maybe something else the app is causing to run. 

A Rails app will spike when it starts up but should settle down as it waits for incoming connections. If you have periodic tasks it's performing you should see those cause the CPU activity to spike again then drop when the task ends.

You're on a MacBook Pro. How much RAM do you have? Maybe your apps are running low and having to swap out too much? That would affect your overall system performance making the CPU work harder, causing it to heat up. A MacBook Pro's hard disk is designed for battery efficiency, not high performance, so if you're hitting the disk hard with a lot of database I/O, you could be heating the machine up and causing the apps to wait due to record locking or some sort of contention.

There's a lot of different things that can cause your machine and apps to slow down, and you haven't really given us a lot to work with, so those are some general ideas of what I'd look into.
I have noticed this also and was able to pin-point it.. If I run top -o cpu, and then open another terminal window and run IRB, and then close the terminal window without exiting out of IRB, then suddenly top shows a ruby process at around 90% CPU. If I do the same experiment but exit out of IRB prior to closing the window, there is no 90% ruby hog.

So, apparently we need to be careful to not close terminal windows unless we have properly exited out of ruby programs.