>Hi,
>I have a form where the user may scan or enter a barcode of a merchandise item. When the barcode is entered the method that fires re-queries a view to extract information such as account, inspection requirements, etc., that relate to the merchandise scanned. Some of these info need to be displayed on the screen or accessed on line and others may need to be updated. My problem is that the requery process takes so much time. The user should not wait that long to scan the next item.
>
>The base table of the view currently contains 370,000 records. All other info come from three other chilldren tables. All the tables are Rushmore optimized to my knowledge. I am sure that some of you deal with larger tables. How do you get around this problem?
>
>I am open to an alternative interface design, if anyone may suggest. By the way, I am using Visual MaxFrame framework.
>
>Thanks in advance.

1. How long is "so much time"?

2. Could you give us an outline of your environment - type of network (if any), speed of workstations, OSs, etc.

3. Could you post some samples of requery code/view definitions etc.

A couple of general points:

- are you using parameterized views?

- sometimes, when using frameworks, you can place code in the wrong method, and then your code gets executed multiple times for each form refresh. Perhaps you could put a strategic WAIT WINDOW in your requery code to see if this is the case.