Hey! Wanna crash your data system?

Then do this:

1. Start with healthy OS, like Win2k Server
2. Install VisStudio Enterprise, namely VB
3. Update to SP3
4. Install either SQL7 or MSDE
5. Install MDAC 2.5 (you sure as hell can't re-install or un-install this so get it right first time)
6. Do some ADO stuff with SQL7 - everybody's happy
7. Uninstall SQL7 or MSDE cause after 12 months you've figured out it's just an upgraded MS Access <-- herein lies the culprit
8. Make decision to use a man's database, like Oracle
9. Try to build connect string with ADODC to Oracle
10. System will hang, with VB going to 100% CPU utilization. It'll stay like this for days if you let it.

Debug/rebuild steps

1. Try to re-install MDAC 2.5 to catch missing or corrupt files. It immediately complains that you are one ignorant bastard for even thinking you've got to re-install MDAC, ever. Then it refuses do it.
2. Try to un-install MDAC so you can re-install it. No facility for uninstalls. Period. Scan through registry lookin for MDAC stuff to delete, but you'll never catch it all.
3. Ok, uninstall VB - totally.
4. Re-install VB. Works fine.
5. Re-install SP3. Complains that "Visual Studio common dir does not exist" and fails.
6. Start up half-assed install of VB, and try some ADO stuff again. Hangs once again on connect string build.
7. Throw computer in lake. Cuss out MS development real loud like, so maybe they'll hear a customer for the first time.
8. Submit tons of bug reports to MS. Wait 3-4 weeks for reply. Reply is a question like "how fast is your cpu". Wait another 3-4 weeks for another stupid question, in order for them to answer you original question.
9. Respond to email from MS that development support will expire in 14 days, and MS wants $2000 for renewal.
10. Drop support issue and start using Delphi and Oracle.
11. It works.