>>>We have developed an application used by a client on a LAN with acceptable performance. It was then installed on a WAN with the result being the Login screen takes more than 10 minutes to display.
>>>
>>>The application tables are not free tables but are in a database. There network specialist said it looks like the dbc and dcx files are being transferred over the network. Is this how an application behaves on a WAN? Would this make a difference in performance? Are there design issues that are relevant to WANs but not to LANs? WHere could I find out more about this issue?
>>
>>Hi Shane,
>>
>>There are a few issues here. First of all, how is the WAN connected. Second, you don't specify but I'm assuming the EXE is on the network. If so, you are also sending the entire application down the line. Need a bit more info, but the first thing I can suggest, if you haven't already, is install the EXE on each user machine. HTH
>
>The speed of your internal LAN would be 10 mb/sec or 100 mb/sec if your are on ethernet and 16 mb/sec if you are on token ring. The fastest speed of the WAN would be 4.5 mb/sec (T3 connection, anything faster like a fiber connection would be considered a MAN or LAN). WAN speeds as low as 56 kb/sec are not unusual. The first thing to do is as Colin suggested. Then if you have static lookup tables move those to the local machine also. Limit your use of grids that do not have some control on the number records displayed.
>
>Robert

The program is located on the local drive. Only the data is on the WAN.

The network specialist said the program was only able to transfered 1.5MB of data in 40 minutes. Does that sound right (655 bytes/sec)?

Would there be less network trafic if I used free tables?

Is it even realistic to get a VFP app runing over a WAN at 655 bytes/sec?