You can find these in System.Data.SqlClient.TdsEnums using Reflector.
DISCLAIMER: These could be out of date or wrong! I've just listed them here because I couldn't find them on Google.
18456: Logon Failed
18488: Password Expired
HTTP 404 error in IIS 6 on new ASP.NET application install
If you're putting together an IIS 6 box and you're getting 404 errors on all your ASP.NET applications, do the following:
1. Open IIS Manager on the IIS box
2. Expand the computer_name node
3. Click on Web Service Extensions
4. Ensure the Status for ASP.NET v2.0.50727 is Allowed
1. Open IIS Manager on the IIS box
2. Expand the computer_name node
3. Click on Web Service Extensions
4. Ensure the Status for ASP.NET v2.0.50727 is Allowed
Repair of a corrupt Microsoft Access ADP file
1. Open a brand new ADP file.
2. Enter the connection details when prompted.
3. File->Get External Data->Import
4. Select the corrupted ADP file
5. Select all Forms, Reports, Macros, Modules that you need. Click OK
6. If all goes well, you'll have a working ADP file again. If it doesn't go well, try being more selective with the imported data. You might have a badly corrupted Report that you'll have to skip.
This may give you some more ideas.
2. Enter the connection details when prompted.
3. File->Get External Data->Import
4. Select the corrupted ADP file
5. Select all Forms, Reports, Macros, Modules that you need. Click OK
6. If all goes well, you'll have a working ADP file again. If it doesn't go well, try being more selective with the imported data. You might have a badly corrupted Report that you'll have to skip.
This may give you some more ideas.
Firefox CSS div / box model problem
The Problem: You've structured your page using a whole bunch of divs. Perhaps #top, #centre, #footer. Everything is inside #wrapper. Inside #centre you have several divs of class ".container". The containers comprise mainly of images - some of which are loaded from external sites. The containers are floated left so that their internal contents can also be floated. This is a standard scenario.
In firefox (1.5-2.0+), particularly if the images load slowly, there is an "overlap" effect, by which as the container divs fill up and expand themselves, the #footer, which has already been rendered, appears underneath the container divs.
In other words, the footer shows up first because it is just text and is rendered quickly. It will appear at the bottom of the page, say at 1000px down the page. The bug or feature in firefox means that as the divs above it expand they run down the page over the top of the footer which stays static in the place it was first loaded.
The Solution!
It is imperative that for every floated box/div, you also have specified a clear parameter. For things like content containers, or main page containers you can use clear: both. And for more complex layouts where you are mimicking tables, you can use clear: left or clear: right.
In my particular situation, I had not floated the #center div, and thus had also not specified a clear param. So, leaving #wrapper to take care of the centred positioning, I added the following lines to #centre:
float:left;
clear:both;
And for good measure, I added these to .container:
clear:both;
This seems to ensure that firefox will correctly push already rendered boxes down the page. Not sure if it's a bug or not. I guess it is, since in my understanding, divs have clear:both set by default, i.e. they are designed to act as paragraphs. I have seen other fixes such as the clearfix and the setting of height to 100%, but these didn't work for me. Perhaps they didn't apply.
Anyway, deep sigh of relief.
In firefox (1.5-2.0+), particularly if the images load slowly, there is an "overlap" effect, by which as the container divs fill up and expand themselves, the #footer, which has already been rendered, appears underneath the container divs.
In other words, the footer shows up first because it is just text and is rendered quickly. It will appear at the bottom of the page, say at 1000px down the page. The bug or feature in firefox means that as the divs above it expand they run down the page over the top of the footer which stays static in the place it was first loaded.
The Solution!
It is imperative that for every floated box/div, you also have specified a clear parameter. For things like content containers, or main page containers you can use clear: both. And for more complex layouts where you are mimicking tables, you can use clear: left or clear: right.
In my particular situation, I had not floated the #center div, and thus had also not specified a clear param. So, leaving #wrapper to take care of the centred positioning, I added the following lines to #centre:
float:left;
clear:both;
And for good measure, I added these to .container:
clear:both;
This seems to ensure that firefox will correctly push already rendered boxes down the page. Not sure if it's a bug or not. I guess it is, since in my understanding, divs have clear:both set by default, i.e. they are designed to act as paragraphs. I have seen other fixes such as the clearfix and the setting of height to 100%, but these didn't work for me. Perhaps they didn't apply.
Anyway, deep sigh of relief.
Making IE6 Behave With Cookies: P3P How To
If you've found this page then you've come up against IE6's privacy features. Namely that cookies are getting blocked and you need them not to be. Perhaps you need frames in your site, perhaps you're into affiliate marketing, but either way the cookies need to make it to your valuable surfer's computer!
At first Google search I was not impressed. If you want to pay around US$100 you can get software to do it for you. There was no way I was going to pay. For starters, I believe almost everything on the web should be for free, and secondly I knew in the back of my mind that I could get my head around an XML schema for less than $100.
So what do we want? A minimal P3P file that just works! When do we want it? Now! Let's face it - we just want our damn cookies to be written to a machine running IE6. I'm not saying privacy isn't important but the firefox/mozilla implementation works just fine for the majority.
So after a bit more searching around I found p3pbook. It's the accompanying website to what looks to be the definitive book on this stuff. They've got lots of examples and this is the most straight forward site I've found on the matter.
If you don't want to wade through the W3C Spec, this example document from the P3PBook shows you all the items of the schema. If you're serious about writing your privacy policy in perfect detail then you will have to check the offical W3C spec to understand the definition of each schema option.
Useful links
http://www.oreillynet.com/pub/a/javascript/2002/10/04/p3p.html
At first Google search I was not impressed. If you want to pay around US$100 you can get software to do it for you. There was no way I was going to pay. For starters, I believe almost everything on the web should be for free, and secondly I knew in the back of my mind that I could get my head around an XML schema for less than $100.
So what do we want? A minimal P3P file that just works! When do we want it? Now! Let's face it - we just want our damn cookies to be written to a machine running IE6. I'm not saying privacy isn't important but the firefox/mozilla implementation works just fine for the majority.
So after a bit more searching around I found p3pbook. It's the accompanying website to what looks to be the definitive book on this stuff. They've got lots of examples and this is the most straight forward site I've found on the matter.
If you don't want to wade through the W3C Spec, this example document from the P3PBook shows you all the items of the schema. If you're serious about writing your privacy policy in perfect detail then you will have to check the offical W3C spec to understand the definition of each schema option.
Useful links
http://www.oreillynet.com/pub/a/javascript/2002/10/04/p3p.html
Subscribe to:
Posts (Atom)