>Just ran into a head-scratcher at customer site. We've got a VFP application that connects to a MS-SQL server. Program had been working fine when the program files were hosted on a Novell file Server. After migrating the application folder to a Server 2012 fileserver in a shared folder, it stopped working -- the error suggests that the application cannot connect to SQL Server -- either that connection couldn't be established, or if authentication with SQL server is failing. If we copy the application folder to a local drive then run the program from local drive, the program starts working -- there have been no other changes made. The SQL Server was installed to work with SQL Authentication, and the DSN has been configured accordingly -- test within ODBCAD32 (the one in the SysWow64 folder) indicates the DSN definition is OK. In short, the program works fine program files are hosted on Novell or local drive, but not when hosted on Windows file server. Any ideas of what might be happening?


FWIW, I had exactly the same issue with a small application I wrote in C#, the source was in a network share and when within Visual Studio I created the connection and a preview of the data, everything seemed ok, it would connect to sql and retrieve the data without problem, but as soon as I tried to run the code, either by "debugging" or by actually running the exe, I would get an error (I think the error was that it could not login to sql server, so this might be different), then I found out that by copying the exe to my local drive it would work without issue, and as I did not have time to waste, I just changed the output folders in Visual Studio to point to a local drive for both debug and release and that "fixed" my issue, but I never found out a proper solution, so I hope you do and you share :)