Well that's a bummer. Even so the workaround seems easy enough.
Generally when I do a small project like this for someone I give them the option to have me do the install for them because "things can happen"...as you've just experienced....and having something like remote desktop, vnc, or pcanywhere with them is handy too so that you don't actually have to go into their location.
Anyway hopefully you got it running for them now? And yes it might be a little more hassle for the install - but this is a one-time thing. Once it's going SQL will be vastly more stable than Access or VFP tables, so in the long run I think you still made the right choice.


>To everyone who responsed to this....
>
>I have spent the last 2 weeks creating tables and writing scripts in SQL to support a small C# WinForms contact management
>application a client hired me to write.
>
>I posted this thread because I thought that 1) SQL was overkill, and 2) every time I have tried to install any version of SQL there
>are failures.
>
>Sure enough I went to my client's office at lunch to install SQL and the app. The SQL installation failed. This is the reason:
>http://support.microsoft.com/kb/968749
>
>Notice the "workaround". Notice that to fix this I will have to download, install, and run some other tool, and then hope that this
>will be all of it.
>
>This is exactly why I didn't want to go with SQL, or any other server based DB. Had I gone with VFP or Access, my client would
>be using his software right now.
>
>Now some of you will inevitably say, have him do this, or ask him to install that... This guy is an Allstate insurance agent with the
>computer literacy of my 7 year old. He expects me, rightfully so, to show up, push a few buttons, and voila! - instant software.
>
>Al have always held to the rule of using the right tool for the job. SQL was not the right too for this job.
>
>
>
>>I'm working on a small MS Access to C# WinForms conversion project. I have to decide which database to use. The client will most likely want to take the data home, so SQL will not be an easy option.
>>
>>I could do it in Access, which he knows and I hate, or I could do it in VFP, which I know. It's going to be one of these two, as I'm not
>>interested in learning another DB at this point.
>>
>>I guess I'm just looking for thoughts....