>>What part of the performance is "slow" - retrieving the data, or displaying/navigating through it? I ask because in the past I've had users complain of "bad performance", when they're scrolling to the bottom of a grid with many rows by clicking on the down arrow and holding it down, rather than dragging the thumbnail or clicking between the thumbnail and the down arrow. Sometimes with issues like that it's just a matter of a few minutes' training.
>>
>>You say you have a workstation where performance is good. Can you test what the performance is like while remote-controlling that workstation? That will isolate whether it's a problem with Remote Desktop or whether it's lower performance in the Windows 2008 R2 session compared to the separate PC workstation.
>
>Data is presented in the grid with acceptable time (first load). Every subsequent operation i.e. typing a letter in the text research area is shown with a noticeably delay.

Is this some sort of incremental search - where you type a search string in a textbox, and you have code that navigates automatically to the nearest match in the grid?

If so, what is slow?

- the typed letter arriving in the textbox
- the record pointer in the grid moving to the correct row
- screen refreshes of the grid (and/or textbox)

If it seems to be some sort of redraw speed issue, you can experiment with putting a line

BITMAP=OFF

in your app's CONFIG.FPW file. IIRC this was introduced in an SP of VFP6 in order to address screen redraw issues in VFP while run in a Terminal Server session.

If it is performance of code to find the right row in the grid we'll need a lot more information:

- What is the database? If VFP, is it on the 2008 R2 server, or some other computer? Is it being accessed via SMB2 from the 2008 R2 server?
- OS of the workstation that performs well, and whether it uses SMB2 to access the database
- Whether antivirus is active on the 2008 R2 server (and/or database server computer, if separate); and what happens to performance if it is temporarily disabled
- What are the parameters of the 2008 R2 sessions - total RAM etc.? Does that server have any performance problems e.g. overloaded disk/high average disk queue length?

At some point it may also be useful to show us the code you use for incremental search, in case there are ways it could be optimized.