>>I'm having the devil of a time getting my app to perform acceptably via Dial-up networking under Windows 95. Multiple megabytes are being transferred from the server to me, even though I've put the run-time library and executable app on a local hard drive. Does anyone have tips to help me out?
>
>Can you tell us more about your kind of protocol you are using? Are you using and ODBC driver, HTTP, HTML, socket?

How can I tell which protocol I'm using? The properties dialog of the connection lists NETBUI, IPX/SPX compatible and TCP/IP, and they are all checked. I am dialing in to my client's server directly, without going through the Internet, so I don't think I'm using TCP/IP. Their server is Window/NT, so I think I'm using NETBUI, but I'm not sure.

I am not using an ODBC driver.

This is a multi-user application that runs fine on the local network, but takes a minute and a half just to open the dozen tables when using Dial-up Networking at 24K baud. I dial in using the connection dialog for their server defined in my Dial-up networking folder. This connects and logs me on to their server. I then map a network drive to the root directory where the application is on the server. I then select the application from the local machine's Start/Programs menu. The EXE, the Foxpro 2.6 run-time library, the CONFIG.FPW file, the resource file, and the library DLLs used by the application are all located in the start-up directory of the local machine. All I do is set the Foxpro path to the root directory on the mapped network drive. Is this the best I can do, or am I doing something obviously wrong? The application is unusable remotely as the situation currently stands.

Thanks a million for any help you can provide.

Ed