I have an interesting problem with an application that has normally resided as an .EXE located on a network drive. The application has been invoked by having a shortcut on the desktop of workstations.
When I try running the app separately on each workstation and keeping the MDB database file on the network drive, errors occur that are consistent with the wifi connection dropping out.
Is it possible that when the .EXE is run from the network drive, that Windows is actively ensuring that the wifi connection to this drive stays alive? This is the only explanation I can think of for why this is occuring. I notice when you look in the task manager it keeps track of the file location for the programs being run.
