Scientific software package works fine with SQL Express 2008 R2 on developing (mother) PC and Admin login mode, but difficulties are found elsewhere during installing and deploying on the client PCs.
We have used from year 2000 BDE (Borland Database Engine), which worked fine until now, but recently customers had been installing problems with Vista, Windows 7 and the local administration rights or permissions.
Thus I thought to test NT AUTHORITY\NETWORK SERVICE authentication, as this system is hopefully working again decades with coming new Windows versions. As not need to touch databases, ADO and authentication
matters during last decade, I’m newbie with those topics.
Worked now few days with this problem, installed and unistalled SQL servers according to instructions, tested different connecting strings and now cannot found correction.
Solution is maybe and hopefully simple.
Attached is log data cut from (old and many times corrected) the main mother XP platform in Admin and Client (Guest) modes.
Same tests are done also with fresh XP installation on VirtualBox.
Used connecting strings are presented inside log files:
Main mother XP at Admin login:
2010-08-20 08:24:45.82 Server
Server local connection provider is ready to accept connection on [ \\.\pip
View Complete Post