HKDevTips

From my experience, try to avoid turning on both AutoIncrement (in DataColumn) in .NET and Autonumber in MSAccess at the same time. As somehow there is just no communication between them. They just work on their own. For example, when you have records in ACCESS having ID (1,2,3,4) and suppose the next ID be 10 (as doing some record add and delete before). AutoIncrement in .NET just don't know about it as it's AutoIncrementSeed can just automatically set to 5. Then 10 vs 5, I hope you can see how the problem being occurred. So avoid having them both at the same time.

When working with .NET, you may wonder the difference between Literal and Label . Actually, when both controls are converted to become HTML, Label will add a pair of <span></span> tag, while Literal keeps everything unchanged. So most of the time if would be better to use Literal instead of Label for the sake of simplicity.

For those folks out there using Windows Server 2003 SP1 Build 1277 along with the SQL Server 2005 December CTP, you may be unable to install SQL Server 2005 with the following error: Microsoft SQL Server 2005 Beta 3 Setup The SQL Server System Configuration Checker cannot be executed due to WMI configuration on the machine SI4P64LF3-05 Error:2147749907 (0x80041013). The cause of this error is a corrupt install of WMI, caused by upgrading Windows Server 2003 to SP1 build 1277. To fix this issue, copy the following into notepad and save it with either a .cmd or .bat extension. Then run the script to re-install WMI: %SYSTEMDRIVE% CD %windir%\system32\wbem Mofcomp.exe cimwin32.mof Regsvr32 /s wbemupgd.dll Regsvr32 /s wbemsvc.dll wmiprvse /regserver If that doesn't work, try the info here posted on MSDN . Ref: http://blogs.msdn.com/jpapiez/archive/2004/12/09/279041.aspx

  When Office2003 couldn't find file SKU011.CAB: regedit -> [HKEY_LOCAL_MACHINE] -> [SOFTWARE] -> [Microsoft] -> [Office] -> [11.0] -> [Delivery] -> {90000409-6000-11D3-8CFE-0150048383C9} -> [CDCache] change to [0] .... Done!

A nice trick provided by Aaron Stebner Ref: http://blogs.msdn.com/astebner/archive/2005/12/08/501885.aspx I have heard from a few customers who have tried to uninstall beta versions of SQL 2005 and then install the final release and have run into errors with both the beta uninstall and the final release install. I have already described the most common uninstall error and a suggested workaround in this previous blog post (an error reading property "Installids" from the cache and/or an error writing property "flagCommit" to the cache). I wanted to address one of the most common final release install errors I have seen - a duplicate instance name error that causes SQL setup to fail and rollback. It is pretty easy to tell if you are running into this error if you launch SQL setup directly and step through the SQL setup UI. However, if you are installing SQL Express as a part of Visual Studio 2005, setup runs in silent mode and you will only see a generic error bubb...

Simply remove files in: Program Files\Common Files\DirectX\DirectInput\User Maps\*.*

Just got some ideas for redirecting Apache request to IIS, if anyone make this work, please let me know. RewriteEngine on RewriteRule ^/(.*\.asp)$ http://localhost:81/$1 [P]