You can try using SQLDMO to detect the SQLServer instances. Vasudevan Deepak Kumar Personal Web: http://www.lavanyadeepak.tk/ I Blog At: http://www.dotnetjunkies.com/weblog/deepak/ http://deepakvasudevan.blogspot.com/ http://deepak.blogdrive.com/

If I recall correctly, you can do the same as you do with Windows file sharing: create an account with the same username and password on the server as on the client computer. Integrated Security will fall back on NTLM authentication which should succeed if the passwords match. This is very hard to maintain, of course. When adding the account (or group) to SQL Server, to authorize the account to connect, use the server machine name where you would use the domain. Stability. What an interesting concept. -- Chris Maunder

www.codeproject.com/netcf[^] cheers, Chris Maunder Remember that a lone amateur built the Ark. A large group of professionals built the Titanic.

I ,finally after lot of search, found what is the problem. It's a bug in office XP and office 2003. When you have installed the english version of office and you regional settings are not the same then you cannot call some functions, especially in Excel, and you have to use InvokeVerb so you tell with what exactly Culture Info you want to call the method. I lost really lot of time searching for this. By the way in office 2003 the PIA work good, you don't have to do the copy you have told, in Office XP there is this problem. Thanks a lot From Greece: Dimitris Iliopoulos dimilio@yahoo.com

Portable .NET supports both AMD64 and IA64 . http://www.southern-storm.com.au/portable_net.html[^] top secret xacc-ide 0.0.1

You can write your own your custom class and store printer setting in it and serialize it. Mazy "I think that only daring speculation can lead us further and not accumulation of facts." - Albert Einstein

Take a look at DevArticles[^] This might help... Free your mind...