That's why it looks funny!

by Ted Jardine Friday, September 29, 2006 10:16 AM

 I've been meaning to make a post on this one since I first read it a couple weeks ago: Raymond Chen of OldNewThing points out when to use "shutdown" and when to use "shut down". I've always somehow intrinsically known that for some reason the similar "setup" works in certain contexts, while in others, "set up" feels right - but have never bothered to work out why. Now I know. It's because the former is a compound noun while the latter is a verb+particle.

Turns out someone else points out that this is a particular pet peeve of his:

Repeatedly in the last few days, I have read the word setup used as a verb. It's not. It's a noun. The verb form is two words: set up. You can set up a setup, or you can set a setup up, or this can be a setup, but you never setup a user’s computer.

In computerese, setup can also be the name of a program, in which case you can run setup, or run the setup program, but it's still not a verb.

There, I feel better now. Back to solving more important problems.

It's times like this that I really wonder how we ever figure English out. I speak Cantonese as a very second language, and know that I must thoroughly butcher it when I think of all things about English that I just know.

Why is this in a Developers' Blog? Well, in the event you send any correspondence to us, take note so that you might not cause serious angst (and see this) in us persnickety snobs (and be nice, point out any grammatical errors in any of the above so I can fix 'em real quick).


Backport MS SQL 2000 database to version 7

by Ted Jardine Tuesday, September 26, 2006 11:19 PM


In looking around for the best/easiest way to backport a MS SQL 2000 database into MS SQL v.7, it seemed most of the responses basically resorted to either script it or "upgrade to 2000". For i.e. Microsoft says:

To work around this problem, use the data transfer utilities in SQL Server 2000, including Data Transformation Services (DTS) and the BCP utility, or create linked server queries to transfer data from a SQL Server 2000 database to a SQL Server 7.0 database. You can also upgrade from SQL Server 7.0 to SQL Server 2000, and then back up and restore the database on the computer that is running SQL Server 2000 server. (from;en-us;824423)

On the small chance that some other poor soul has to do the same, here's how I did it (as upgrading was unfortunately not an option for this client):

First, I scripted my tables, views, stored procedures, etc. as necessary, while making sure to check "Only script 7.0 compatible features." While I was aware of several items that were added to SQL Server 2000 (and thus avoided using them during development), two gotchas for me was finding out belatedly that SQL Server v.7 also does not support Cascading Updates/Deletes or SCOPE_IDENTITY(). The scripting tool still however includes these, so there's some manual editing of the scripts to modify them so they run on v.7 (and some development time later so that your app takes care of cascading deletes).

Then I wrote a batch file to BCP the data out of the SQL Server 2000 database:

@echo off
rem "Usage: MyBCPScript.bat Password"
@if "%1" == "" goto usage
echo Password : %1 pause
Echo coping tables from MySampleDatabase ...
bcp MyDb.dbo.Organization out d:\SQL\Organization.bcp -n -P%1
etc.... for all tables in database
goto end
echo Usage: MyBCPScript.bat Password
echo Finished!

Then I wrote a batch file to BCP the data into v.7:

@echo offrem "Usage: MyBCPScriptsRestore.bat Password"
@if "%1" == "" goto usage
echo Password : %1
Echo resoring tables to v.7 database ...
bcp MyDb.dbo.Organization in D:\SQL\Organization.bcp -n -P%1
etc... for all tables in database
goto end
echo Usage: MyBCPScriptsRestore.bat Password
echo Finished!

Run the first script from the command line to export the data:

D:\MyBCPScript.bat UltraSecurePassword

...and run the second with:

d:\MyBCPScriptsRestore.bat UltraSecurePassword.

Presto! MS SQL2000 database backported with data to v.7! Of course, the order of tables to restore in the second script is important for any related data. Note that with the scripts, I now have the ability to get the latest data later by simply running the batch files again right before going live with the v.7 database. There are some other gotchas that I didn't mention, most due to my incorrect assumptions that kept forgetting that version 7 was released around the same time as Win98. Namely, v.7 doesn't run on XP or on Win2003. Argh. So up with a Virtual Server to take the time machine back and install an instance of Win2000, which does run SQL v.7. However, even then the Enterprise Manager doesn't work for altering a database without upgrading to the latest service pack (after wasted time determining the cause of an error message that seems to have nothing to do with needing a service pack update -

Btw, this post comes courtesy of Windows Live Writer. After TWO days of attempting to post on and regularly getting a "Could not connect to Saving and publishing may fail. Test connection now" warning just as I was about to post, I gave up. Lo and behold, the blogger api is still up and running so along comes Windows Live Writer to save the day!


Inmagic changes leadership

by Administrator Wednesday, September 13, 2006 12:03 AM
Inmagic, Inc. has named Paul J. Puzzanghera as President and Chief Executive Officer, effective immediately. He has served as Inmagic's Vice President of Professional Services since coming to the company in 2003. Phillip L. Green, who has been Inmagic's President and CEO, has been named Vice Chairman. He will remain in a full-time operational role with the company.

Tags: News

by Administrator Friday, September 08, 2006 10:48 AM
Brilliant quick reference site that finds programming documentation as you type (HTML, CSS, Javascript, more). Just needs C# and VB.NET. C'mon somebody. Anybody. Not me though. I'm a busy man.


Ah! Ah! Apostrophe!

by Peter Tyrrell Thursday, September 07, 2006 5:36 PM

Whilst warbling on about WebPublisher security today with Ted Jardine (developer extrordinaire), he innocently asked me a question about apostrophes. As in, "does one require an apostrophe after 'dll' when indicating more than one?" (We developers toss around words like 'dll' all the time. It makes us feel cool.) I hazarded that dll's was just plain wrong and that DLLs would be correct. As it happens, my guess is backed up by the mighty Wikipedia: For the plural of abbreviations, an apostrophe is widely regarded as incorrect, so CDs is preferable to CD’s. And so on. Well that's great. Aren't I so smart. But then later today I noticed, to my horror, that I have been abusing the apostrophe in this very blog! O miserere me! The blog title has been "Andornot Developer's Blog" yet there are multiple developers blogging. Well, it's mostly me, I confess, but aaaaagghhh! So I'm changing the title to Andornot Developers' Blog. Aah. Harmony and Balance restored.


Month List