So I just wasted 2 1/2 hours tring to figure out the WHY the Tab ordering was not working on my Form (C# project Visual Studio 2010).
No matter what I did the order DID NOT CHANGE. There are all kinds of controls like Groupboxes, Panels with Controls inside Controls. No big deal. The View -> Tab Order feature made NO DIFFERENCE at all!!
The only way the tab Order worked was by actually updating the DESIGNER to order the Controls in the way I wanted! Like this...
this.pnlSubAbc.Location = new System.Drawing.Point(3, 344);
this.pnlSubAbc.Name = "pnlSubAbc";
this.pnlSubAbc.Size = new System.Drawing.Size(562, 212);
this.pnlSubAbc.TabIndex = 2;
this.pnlSubAbc.TabStop = false;
this.pnlSubAbc.Text = "Products Carried";
Hope this Helps someone else out there.
It is very very simple to avoid p page refresh in post-back . To get this we just have to use ASP "Update Panel Control" it will not refresh the page again and again on post-back.
Here is an example.
<asp:UpdatePanel ID="pnlPageRefresh" runat="server">
<asp:DropDownList ID="DropDownList1" runat="server" AutoPostBack="True">
<asp:TextBox ID="TextBox2" runat="server" AutoPostBack="True"></asp:TextBox>
<asp:RadioButtonList ID="RadioButtonList1" runat="server" AutoPostBack="True">
<asp:Button ID="btnSave" runat="server" Text="Button" />
After using this your page will not at all refresh again and again on post-back. Your code will work fine but refresh flickering will not occur.
If you need to debug a WCF Server, or somehow need to step into code on IIS, you will need to do the following to prevent the message “Unable to automatically step into the server. Unable to determine a stopping location”. The message might be slightly different but generally it means you can't debug in IIS!
It turns out that Visual Studio 2010 comes with a default setting to debug ‘Just my code’.
To correct the problem, go to Tools – Options – Debugging – General and switch off the option ‘enable just my code’.
And of course don’t forget to set debug="true" in the web.config file of the webservice. Double check your publishing Transformations too if using any, as that might be removing the debug="true" property in your web.Config file.
This will hopefully help someone else out there!
I came across a challenge this week. Migrating Blob data from Oracle to SQL Server. I used MS Access for this since I could create an ODBC DSN to each and then have the best of ALL worlds. That is review the data, count the records and write very simple code. The link below is excellent and worked perfectly for what I needed for dealing with the Blobs.
How To Read and Write BLOBs Using GetChunk and AppendChunk: http://support.microsoft.com/default.aspx?scid=kb;en-us;194975
The process I used for the Blobs was this:
1. Copy the data from Oracle to SQL exluding the Blobs Column.
2. Export the Blobs to File using the ID field as a key like (ID) & FileName. FileName was a column in my Oracle table so that was nice and pretty well needed so you can Identift the MIME (file type like XLS, DOC, PDF).
3. Finally Update the SQL Server table using File to Blob.
I had some other "things" in the code to deal with missing files from the Blob column but that was simple.