>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?

No matter where the program files are stored - Novell, Server 2012 or local - the program itself is running on the local client. The SQL server should not be an issue because it's always accessed from the client machine, presumably using the same credentials.

Accessing a SQL server probably means creating temp files. Ideally those should always be on the local client but may not be the case for you. If temp files are being created on the same drive/share as the EXE then they would be created on the Windows server. If there are any permission issues for temp files that could "break" SQL operations. Can you test with admin privileges on the Windows share, if you haven't already?