You searched for the word(s): userid:593385

More Search Options

RSS Available

• Re: Could not find control 'xxx' in ControlParameter 'yyy'

  I think you may have a problem in your design! How can the gridview , which is not populated, bind to a datasource, which in turn depends on a parameter sourced from the very same GridView (which, as I said, is not yet bound)?. Wouldn't the sequence of events be: (During PageLoad() ) Call GridView.DataBind Call SQLDataSource to build recordset SqlDataSource starts looking for parameter 'hours' Error message since there is no GridView yet, so therefore there is no parameter 'hours'

  Posted to Data Presentation Controls (Forum) by PhilM99 on 6/21/2008

• Re: Could not find control 'xxx' in ControlParameter 'yyy'

  Sounded familiar... so I found an example where I did exactly that, (I think). There's no code-behind, either: ... in the gridview <asp:TemplateField HeaderText= "Next Status" SortExpression= "NextStatus" > <EditItemTemplate> <asp:DropDownList ID= "DropDownList1" runat= "server" DataSourceID= "NewStatusesSqlDataSource" DataTextField= "InspectionStatus" DataValueField= "InspectionStatus" SelectedValue= '<

  Posted to Data Presentation Controls (Forum) by PhilM99 on 6/19/2008

• Re: Could not find control 'xxx' in ControlParameter 'yyy'

  Whoops, forgot it is in a row. You can problably find every instance of your drop downlist in the gridview rows, if you know which cell it is in. But as you have figured out, every one has a different name. Here's some code where I was looking for a checkbox in every row in my gridview. For Each InspRow As GridViewRow In InspectionGridView.Rows If InspRow.RowType = DataControlRowType.DataRow Then Try selbox = CType (InspRow.Cells(0).Controls(1), CheckBox) If selbox.Checked Then 'Some code

  Posted to Data Presentation Controls (Forum) by PhilM99 on 6/19/2008

• Re: Could not find control 'xxx' in ControlParameter 'yyy'

  Yeah, your reasoning is sound. Although, you could display the page in question, view source, findout what the ID for the drop downlist is, becuase some part of it must be missing. But what I always do is: Dim dll AS DropDownList 'Create a variable to hold the ddl ddl = GridView1.FindControl("DropDownList1") 'Point the variable using the FindControl of the GridView (not the page). If Not IsNothing(ddl) Then 'Protect against Not Found, such as when GridView displays ReadOnly

  Posted to Data Presentation Controls (Forum) by PhilM99 on 6/19/2008

• Re: Could not find control 'xxx' in ControlParameter 'yyy'

  I'm puzzled. You say you have no master pages or anything, so why even use code behind to set this up? You probably should have your data source directly reference the ControlID. If you try that, are you getting an error or something? I don't believe you need any code behind, which is probably just confusing. Unless you're trying to do something else. Here's some sample code for that: < form id= "form1" runat= "server" > < div > < asp:DropDownList

  Posted to Data Presentation Controls (Forum) by PhilM99 on 6/19/2008

• Re: DatakeyNames ... Procedure or function has too many arguments specified

  So, the problem is that you need the datakeynames field for the select to work. But because the field you need is also the primary key, then the SQLDataSource automatically adds it to the delete paramters as well. But your stored proc does not expect it, so poof- the error message. I just went through that because the stored proc parameter name in my program does not match the field name. So even if I leave out the delete parameter specification, I get the correct delete parameter specification value

  Posted to Data Presentation Controls (Forum) by PhilM99 on 2/19/2008

• Re: Could not find control 'xxx' in ControlParameter 'yyy'

  Not sure what you are doing to try to populate your database, but if you are using some code in code-behind it's fairly simple... ... Dim ddl as Dropdownlist ddl = MyDetailsView.FindControl("MyDropDownList") If Not ddl is nothing then some SQL stuff using ddl.selectedValue End If It's harder to get the declarative approach to work because although it uses FindControl, it starts at the topmost container and only goes down one level. Do you follow this so far?

  Posted to Data Presentation Controls (Forum) by PhilM99 on 2/19/2008

• Re: How to debug a COM+ component

  Since I have this working consistently now , I guess we'll leave it. I remain totally convinced that the registry cleanup was critical to this (there were dozens of bogus entries from all my development crashes). And since it did not work using the same location for the VB files that now does work, it sort of says it wasn't the load chain problem you describe. But that was useful, I did NOT know that the b.dll folder you described was not searched. So maybe it took both things to get it to

  Posted to Visual Studio 2005 (Forum) by PhilM99 on 1/31/2008

• Re: How to debug a COM+ component

  I've tried it in lots of different places. Normally the dll is created in the folder where the VB6 project is, and it is outside the web project. When you add a reference to it from the ASP.Net project, inter op files are added to the bin directory (my dll is called PFS.dll) so what is added is: Interop.ASPTypeLibrary.dll and Interop.PFS.dll If the PFS.dll is registered, then the VB project runs ok, but as I said I wanted to debug the vbp. I have also tried moving the entore VB6 project under

  Posted to Visual Studio 2005 (Forum) by PhilM99 on 1/30/2008

• Re: How to debug a COM+ component

  Thanks for responding. Yeah, in my case the wrapper (Interop.PFS.dll) was created by using VS2005 to reference the dll (PFS.dll). When run the VS2005 project, it runs ok except it uses the compiled dll and I need to debug the COM dll. So I start VB6 and run the component that created the dll and when I run the VS2005 project I get an error, and am unable to find any help on what it is. "Unable to cast COM object of type 'PFS.AdministratorClass' to interface type 'PFS._Administrator'

  Posted to Visual Studio 2005 (Forum) by PhilM99 on 1/28/2008