The connection string tells Navigator where to find your data.

To fix this, map a drive on the server and change the connect string.

To fix your installation:.

1. Create a mapped drive on the server. For instance, map drive H:\ to C:\Program Files\.
2. Edit fnsql.ini, changing the connection string from C:\ProgramFiles\FN90\data\fn001.mdb to H:\FN90\data\fn001.sql. fnsql.ini is located in the Navigator 9.0 program folder C:\Program Files\FN90.
3. Edit the Target in the desktop shortcut for Navigator on the server. For instance, change C:\Program Files\FN90\fn90.exe to H:\FN90\fn90.exe.

To install Navigator on a peer-to-peer network:

1. Share the C:\ProgramFiles\FN90 on the server so everyone has access.
2. Map drives on all computers, including the server. For instance, if Navigator is in C:\ProgramFiles\FN90, map H: to C:\Program Files\FN90 on the server and H: to {server}\Program Files\FN90 on all the workstations.
3. Do a full installation of Navigator 9.0 on the server. You should be physically at the server. When asked for the path, use H:\, not C:\ProgramFiles\FN90. This will create a desktop shortcut on the server that runs Navigator from H: and a connection string that also uses H:
4. Do a Workstation Installation of Navigator on each computer. Be sure to use the correct path (H: for example).

Note: You will have the same problem (and the solution is the same) if you have a real network with a real server and need to run Navigator while you are sitting at the server.