Thanks for letting us know!

>I'd like to thank all who have contributed to the slow networking. I have noticed one thing to share back. The main culprit (and it shows up mostly in multi-user mode) seems to have been the use of dynamic formatting. When I create data grid, there are a number of optional SETALL options to highlight records e.g records with "*" in a field called TAG are highlighted. Also one to set a strikeout font for records marked "*" in a field called DEL. These dynamic formatting command slow it up massively. Examples:
>
>

>fbrop.grd1.SETALL("DynamicFontBold", "IIF(alltrim(upper(taxstat))='ACC', .t.,.f.)","Column")
>fbrop.grd1.SETALL("DynamicFontStrikeThru", "IIF(del='*', .t.,.f.)","Column")
>

>
>Removing the dynamic formatting has been the most effective edit to speed thing up.
>
>Denis
>
>>>We have a VFP9 database running on networks. In some case, even with only 2 or 3 users and less than 50,0000 records in largest file, this becomes painfully slow. When one logs into the same databse in single user mode, the same system runs like the clappers (same time of day on network - thus it's not the network per se. The offending network has PCs running on Windows 7 Enterprise with Service Pack 1. The network runs on Extreme Networks switches (1 Gbit). Storage is hosted on NetApp.
>>>
>>>When in multiuser mode, the VFP app runs the code:
>>>SET EXCLUSIVE OFF
>>>SET REFRESH TO 1
>>>SET REPROCESS TO AUTOMATIC
>>>
>>>There are no special commands in the config.fpw file. I have tried adding ...
>>>
>>>TMPFILES=c:\work
>>>EDITWORK=c:\work
>>>SORTWORK=c:\work
>>>PROGWORK=c:\work
>>>
>>>but I can't see any files appearing in c:\work so unsure that is working in any case or if it would help?
>>>
>>>Appreciate this is rarther general - but any other ideas to help speed things up?
>>
>>With a NetApp back end, how are you accessing your data:
>>
>>1. Workstation --> Windows file server --> NetApp appliance/SAN
>>
>>or
>>
>>2. Workstation --> NetApp appliance/SAN
>>
>>In case 1 NetApp is being used basically as a fast disk subsystem for ( one or more ) conventional Windows server(s). In case 2, workstations connect directly to the NetApp device without needing an intermediary Windows server.
>>
>>In either case, I'd try temporarily disabling any antivirus real-time scanning on all involved workstations and server(s). If that helps, configure the AV to not scan workstation or server folders that may contain tables or temporary files.
>>
>>If it's case 2, NetApp is presenting an SMB-like interface to the network. Since it is not true Windows it may not be running any antivirus at all; but if it is, try to not real-time scan your data or temp files. There may be NetApp configuration settings for optimal performance and reliability with file-server apps like VFP and MS Access; those may not be the defaults.