Osmotic Web

Want to add a boolean column to an existing table?  Here’s the syntax:

ALTER TABLE  [Table] ADD COLUMN [new_column] BIT;

Is your DropDownList misbehaving (such as not reporting the correct selected item in the selectedindexchanged function when an item is selected and autopostback is set to true)? Check to make sure there aren’t any <form> tags littered throughout the html of the page.

I believe there should only be one asp.net parent server side form tag wrapping all of the html of the body.

Want to use an Access DB for membership and roles? Need to know where and how to install the Access Membership Provider?

The forum thread where I found the solution is here

“you download the kit from this link . Double click on it and follow the wizard. You VC# that you should download from ms website. You can click the link right below the kit. When you open this app…click new project…select from the template Asp.net Access Provider. Make sure you name your project Sample Access Provider and then you won’t have to change the web.config file. Save. Once you do that copy the web.config file. In VWD paste that into web.config. of your new website. Then navigate to mydocuments/vwd2005/projects. Double click on the folder Sample Access Provider and there is another folder and inside that is a bin folder. Copy contents of bin folder to your website…there should be a .dll …plus I copied the .sln file to that same folder in my website AND IT WORKS. “

Just got a strange error that was questioning the authenticity of the view state of the page using the MAC check and something to do with the machine key and questioning if the app was being run on a cluster. What ever the error message was… it wasn’t accurate at telling me what the “real” problem was. So after checking it out for a while, it turned out to be a closing tag, “</form>”, that was commented out in the middle of the html with the actual closing tag at the bottom of the page, where it should be. The form tags should be encapsulating any of your tags that will generate a post back to your server, such as a button (which was the case in my scenario). Well, it turns out that ASP.NET 2.0 was actually reading the closed form tag that was commented out in the middle of the page and therefore excluded and prevented the functionality of the button tag. Thus, the error message. I’ve seen this reading of the “commented out html” issue previously (when asp.net should be ignoring it) in the case with atlas as reported in a previous post. So, watch out for this minor got’cha 🙂

woah… how high was that on the richter scale? the metamorphosis from msn.com to live.com has begun.

A popup error message – "Assertion Failed: elements in children collection should always have nodeType = 1" will occur in IE (not in firefox) when "<!–"  "–>" comments exist in the aspx page and are contained within an UpdatePanel.