>>>>You have any way to remote into his computer and finish the install?
>>No. I talked to him about LogMeIn, but he didn't seem open that giving access to outsiders.
>>
>>
>>>>Probably true that had it been done with VFP you'd got it going - but still you might of ended up back later dealing with corrupted indexes or something.
>>
>>Maybe/Maybe not
>>
>>
>>>>I'm really shocked that you've had such problems installing SQL Server in the past - I've never really had any problems myself - maybe I've just been lucky.
>>
>>I have a boxx at home running Windows Server 2003. I have tried 3 times to put SQL on it. Fails every time with some new issue.
>>I also have a laptop that I had to reinstall Windows on. I can't get SQL to install on it either.
>>
>>I don't think I have ever tried to install SQL and have it go all the way through with no problems.
>
>That's odd - I install it 5 or 6 times a month and never had a problem.
>
>I'd like to hear what kind of results others here have had with SQL Server installs....

We have literally hundreds of MSDE/SQLExpress2005/SQLExpress2008 and full SQL Server2xxx installs around Kanses - mostly at small businesses. Most of our installs are for our own VFP applications (I ALWAYS use SQL Server as the backend no matter what the app) or as part of Microsoft Retail Management System. Many are at businesses that have a total of 1 PC.

We do have basic requirements re:OS, UPS, A/V, and overall system stability before we will attempt an install, but they aren't tough to deal with.

I can't remember any time we've had as much trouble as Kevin has had. It really sucks when you are trying to get a new technology under your belt and out the door and it seems to fall apart - I can feel his pain - been there!

Kevin if I can be of help send me an EMail offline and I'll get on the phone with you or whatever and try to get you on the right track.

And as Kevin G asked elsewhere - why are you using SQL205Express instead of 2008? That is outdated and that is a problem.

>
>
>
>>
>>>>No, I didn't get it running. One thing I failed to mention is that wen I clicked on the bottom error link nothing happened. I left his offic
>>>>and came back to mine and Googled it.
>>>>
>>>>But had I done this in VFP, I'd would have left there paid.
>>>>
>>>>
>>>>
>>>>>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....