Thanks for the breathing advice BOb. Yes, I am calmed down about this already. (bigger problems with a failing hard drive on my primary development machine – ya think it is related to my rant?? {g})

I guess you can say a little more administrative than operational. I installed it on a test box and followed the standard canned install.

So the first thing I did was set up a new DSN to a test database. The DSN connection test would not pass. It was all related to the allow remote connections setting, but that took me a while to figure out even with some Googling and all.

Your comment about NT4 and VFP was also a very tough choice. We did extensive testing on NT4 because we had one client who absolutely needed VFP 8 because of a bug which was not going to get fixed in VFP 7 SP1. He had a major installation with primarily NT4 boxes. It was a deal breaker. We spent a ton of time exercising the application and performing a complete system test. Fortunately, in this case we knew what a complete system test was.

How can I go about certifying everything in MSDE works? I can certainly test out my applications, but what if I am not using a certain type of stored procedure or performing backups a certain way and I realize I need this down the road. I doubt I can verify all of MSDE works on Vista. Microsoft on the other hand has the test tools and test suite to handle this, and the resources to ensure it works. I am much smaller and my bank account is not as fat.

Ok, you can breath now. Also, remember “not supported” doesn’t mean “won’t work.” I think there was a point when VFP was “not supported” on NT 4, but it still worked. Or, you had to put GDI on the Os or something.

Also, what type of troubles have you had with SSE? Has it been admin issues or operational?

BOb