>I'm about to install a FPW 2.6 app into a company with following setup:
>
>Location a: NT File Server with 7 workstations
>Location b: NT file server with 6 workstations
>Both NT servers connected by an ISDN line
>
>Users in both sites will want simultaneous access to the app for viewing/updating so I was going to load the APP in location A and give location B acces to it.
>
>I'm just wondering are the users at location B going to be very ssslow for acessing.
>
>I'd appecaiate any feedback from anybody who has experience of this.
>
>Regartds,
>
>Gerard
Unless you require very fast response times, I wouldn't be too hasty in dumping your existing ISDN link. To get best performance from a VFP app over a slow link:
- Make sure the .EXE is local to all machines. This may mean slight mods to your app so it can access data on a different drive/net share etc.
- Include an appropriate CONFIG.FPW file at each workstation to ensure temporary files are all created on a local hard disk.
- Wherever possible, make sure your queries are fully Rushmore optimizable. Apparently, if they are, VFP makes clever use of index tags to minimize network traffic.
A 128K ISDN link will never be as fast as local 10- or 100BASE-T but you might be surprised how close you can get in real world performance.
Regards. Al
"Violence is the last refuge of the incompetent." -- Isaac Asimov
"Never let your sense of morals prevent you from doing what is right." -- Isaac Asimov
Neither a despot, nor a doormat, be
Every app wants to be a database app when it grows up