You should definitely go to a dedicated server. While NT Server and Workstation are practically the same, they are optimized for different tasks. When the user of the Workstation loads Wordperfect he or she will get priority over anyone else accessing the machine over the network. While you're at it, I would suggest a SCSI hard drive. This will reduce bottlenecks at the server.


>Thanks for the info. I guess I have been mis-informed. This will influence the direction we take in the future. We were thinking of moving to C/S for more speed, but plans are changing (because of this thread).
>
>We were also planning on going to a dedicated server. Currently, we are using a machine running NT Workstation 4.0 as the server. This machine is a regular user's everyday machine. I think going from this topology to a dedicated server running NT Server will improve speed (at least for the non-data server machines). Does this make sense?
>
>BTW, if it appears that I am accusing VFP of being slow, I am not. We do experience a slow down when several users are using the system at the same time. But please understand, when I say a slow down, I am referring to periods of waiting that consist of a second or two. And this is at times when we are pulling up years of historical data and doing a series of calculations. Hey, at these times, it also takes longer to retrieve a WordPerfect document from the WP doc server too.
>
>Take care,
>
>Joe
>
>>Emmanuel and everyone,
>>
>>VFP does NOT transfer the "whole" index over the wire, It gets what it needs.
>>
>>VFP with large tables can out perform any C/S backend I have ever seen. The keyword there is "can" and not does. If the VFP code is written correctly and the correct indexes exist on the data and the network cable is not saturated by traffic and the server is not bottlenecked with work, then VFP can outperform the C/S bakcends.
>>
>>Table size if often quoted as one of the reasons to go to C/S as is performance. These two issues are NOT sufficient motivation for VFP developers. VFP developers should first look into what they are doing that is slowing VFP down.
>>
>>The major reasons that hold water for VFP develoipers to make the move to C/S are;
>>
>> 1) More robust security on the data
>> 2) Accessnig data from diverse applications
>> 3) Robust transactrion servicing
>> 4) automatic live backup of data
>> 5) The company is going that way
>>
>>Performance and table size are not among those reasons.