Datagrid show me only one row.

Question

0.00/5 (No votes)

See more:

Hi, can you help me please. I this crazy string which I need parse to the datagrid, parse is good but in datagrid I have still only one row (last in parse) + header. I dont known why.I need everything in datagrid.

string:
Application: ws_cp_ixnsrv_mm DBID: 845 Status: APP_STATUS_STOPPED Runmode: EXITED Application: mng_dbserver_p DBID: 469 Status: APP_STATUS_RUNNING Runmode: PRIMARY Application: ird_dap DBID: 470 Status: APP_STATUS_UNKNOWN Runmode: EXITED Application: mng_dap DBID: 471 Status: APP_STATUS_UNKNOWN Runmode: EXITED Application: mng_messagesrv_p DBID: 472 Status: APP_STATUS_RUNNING Runmode: PRIMARY Application: mng_scs_p DBID: 473 Status: EXITED Error Application: pulse_collector_02 DBID: 827 Status: APP_STATUS_RUNNING Runmode: BACKUP Application: was_tomcat_1 DBID: 829 Status: APP_STATUS_RUNNING Runmode: PRIMARY Application: svc_nss_p DBID: 850 Status: APP_STATUS_RUNNING Runmode: PRIMARY Application: svc_nss_b DBID: 851 Status: APP_STATUS_STOPPED Runmode: EXITED Error

What I have tried:

my code:

 myProcess.StartInfo.UseShellExecute = False
   myProcess.StartInfo.CreateNoWindow = True
   myProcess.StartInfo.RedirectStandardInput = True
   myProcess.StartInfo.RedirectStandardOutput = True
   myProcess.StartInfo.RedirectStandardError = True
   myProcess.Start()
   label2.text = "Ahoj " & myProcess.StandardOutput.ReadToEnd()
   Dim StandardError As String = myProcess.StandardError.ReadToEnd()

rem Debug.Print Asc(Mid(output, InStr(output, "APP_STATUS_RUNNING") - 1, 1)), Asc(Mid(output, InStr(output, "APP_STATUS_RUNNING") + 18, 1))


        Dim dtable As New DataTable
            dtable.Columns.Add(New DataColumn("Application"))
            dtable.Columns.Add(New DataColumn("DBID"))
            dtable.Columns.Add(New DataColumn("Status"))
            dtable.Columns.Add(New DataColumn("Runmode"))


      Dim outputarray As String() = label2.text.Replace(" Application:", " @Application:").Split("@")
        Dim dRow As DataRow

        For Each recordrow In outputarray
            Dim ApplicationField As String = ""
            Dim DBIDField As String = ""
            Dim StatusField As String = ""
            Dim RunModeField As String = ""

            Dim thisrecordrow = recordrow.Replace("Application:", "@Application:").Replace("DBID:", "@DBID:").Replace("Status:", "@Status:").Replace("Runmode:", "@Runmode:")

            For Each columnfielditem In thisrecordrow.split("@")
                With columnfielditem
                    Select Case True
                        Case .StartsWith("Application:")
                            ApplicationField = .Split(":").GetValue(1).ToString.Trim(" ")
                        Case .StartsWith("DBID:")
                            DBIDField = .Split(":").GetValue(1).ToString.Trim(" ")
                        Case .StartsWith("Status:")
                            StatusField = .Split(":").GetValue(1).ToString.Trim(" ")
                        Case .StartsWith("Runmode:")
                            RunModeField = .Split(":").GetValue(1).ToString.Trim(" ")
                    End Select
                End With
            Next
Dim RowValues As Object() = {ApplicationField, DBIDField, StatusField, RunModeField}

            dRow = dtable.Rows.Add(RowValues)
            dtable.AcceptChanges()        
           

        Next
        GridView1.DataSource = dtable
        GridView1.DataBind()
end sub

Posted 17-Jun-21 5:02am

Member 15251555

Updated 17-Jun-21 5:45am

Add a Solution

Comments

SeeSharp2 17-Jun-21 11:35am

Step through your code and see what is happening.

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

OriginalGriff · Answer 1 · 2021-06-17T05:45:00

Compiling does not mean your code is right! :laugh:
Think of the development process as writing an email: compiling successfully means that you wrote the email in the right language - English, rather than German for example - not that the email contained the message you wanted to send.

So now you enter the second stage of development (in reality it's the fourth or fifth, but you'll come to the earlier stages later): Testing and Debugging.

Start by looking at what it does do, and how that differs from what you wanted. This is important, because it give you information as to why it's doing it. For example, if a program is intended to let the user enter a number and it doubles it and prints the answer, then if the input / output was like this:

Input   Expected output    Actual output
  1            2                 1
  2            4                 4
  3            6                 9
  4            8                16

Then it's fairly obvious that the problem is with the bit which doubles it - it's not adding itself to itself, or multiplying it by 2, it's multiplying it by itself and returning the square of the input.
So with that, you can look at the code and it's obvious that it's somewhere here:

C#

int Double(int value)
   {
   return value * value;
   }

Once you have an idea what might be going wrong, start using the debugger to find out why. Put a breakpoint on the first line of the method, and run your app. When it reaches the breakpoint, the debugger will stop, and hand control over to you. You can now run your code line-by-line (called "single stepping") and look at (or even change) variable contents as necessary (heck, you can even change the code and try again if you need to).
Think about what each line in the code should do before you execute it, and compare that to what it actually did when you use the "Step over" button to execute each line in turn. Did it do what you expect? If so, move on to the next line.
If not, why not? How does it differ?
Hopefully, that should help you locate which part of that code has a problem, and what the problem is.

And we can't do any of that for you - it needs your code running with your data and we have no access to either.

This is a skill, and it's one which is well worth developing as it helps you in the real world as well as in development. And like all skills, it only improves by use!