Use view.Order = 1

So searching on anything not in this list will take 4-5 minutes?

Browse will search record by record using the index or order that you've specified.

If you change the .Order then the .Fetch will arrive at the record much faster.

If you .Put a key field value into the field and you're using the right .Order then you can call .Read and land right on the record directly.

To answer your question  - maybe - it depends on your database, volume of data, etc.

You can use the CS0120 view to call the database directly so if you have other indexes on the table you can find records that aren't indexed by the standard views.

But - like with any database application - if you're not using an index, you're waiting.

Browse will search record by record using the index or order that you've specified.

If you change the .Order then the .Fetch will arrive at the record much faster.

If you .Put a key field value into the field and you're using the right .Order then you can call .Read and land right on the record directly.

To answer your question  - maybe - it depends on your database, volume of data, etc.

You can use the CS0120 view to call the database directly so if you have other indexes on the table you can find records that aren't indexed by the standard views.

But - like with any database application - if you're not using an index, you're waiting.

Ok, where did you find that index? Also if I wanted to query on last posted date, being that's not indexed - you're saying to try CS0120?

The two ways to easily view indexes by view are by using the downloadable Application Object Model or U.I. Info tool located in your Sage 300 program group.  It is organized by module / ROTO ID.  To determine the ROTO ID, you can right-click / properties on the icon making use of the target view - in this case, Orders.

Thank you. Did you have any ideas on this one?

www.sagecity.com/.../calling-net-api-filterfetch-on-customer-view-gives-attempted-to-read-or-write-protected-memory-error