I have a database application that I write on a stand-alone computer and then ship and install on a network. The back-end is on the network server. I could simulate drive letters (F:, L:, N: etc) on the stand-alone and do the linking before I shipped the app to the network. Now I find I must use a UNC path on the back-end link because the users no longer map to a fixed drive letter. I know how to open the link-table manager and put in the UNC path in the file name box.
My problem is that because this UNC path is NOT connected on the stand-alone, I get an error message and it won't save the UNC address. I realize that this UNC wouldn't be valid on the stand-alone, but I want it set before I ship the app so that the users won't have to re-link after they install on the server. I don't have physical access to the server or network.
Does anyone know of a way to put a UNC in the database before it is finally installed on the designated computer? Alternately, does anyone know of a way to simulate a UNC address on a stand-alone computer (virtual drive??) that might get around this problem.
My problem is that because this UNC path is NOT connected on the stand-alone, I get an error message and it won't save the UNC address. I realize that this UNC wouldn't be valid on the stand-alone, but I want it set before I ship the app so that the users won't have to re-link after they install on the server. I don't have physical access to the server or network.
Does anyone know of a way to put a UNC in the database before it is finally installed on the designated computer? Alternately, does anyone know of a way to simulate a UNC address on a stand-alone computer (virtual drive??) that might get around this problem.