Hi!

Well, I would recommend to use views anyway, once you have your own framework. Creating forms with read-only grid for navigation and data editing form, like I propose in my comments below, might be expensive for framework when developing it to be generic. Adjusting framework to use views is less expensive. This is only my very approximate thoughts.

See also comments below.

>>Without grids, filters are ok. There is also another point of view - get rid of editing data in grids at all. Anyway grid is a good tool

>
>Users find convinient to make changes in grid directly. I'm not sure, what kind of alternative interface I can provide. Additional form for editting?
>

Yes. Not a grid, but a form or additional page on the form. See also next comment...

>>just for displaying information, so results of read-only query (either in form of view or in form of a cursor) could be displayed anyway for quick searching or navigation through records.
>>


>>So, when it is posisble to spend more development time on change, I recommend to get rid of editing in grids and use better interface approaches.
>>
>
>What kind of approaches would you recommend? Could you please send me few screen shots of your applications?
>

I could not make screenshots quickly. The idea is simple though.

There are 2 approaches for your case.
1. Use a simple form with navigation buttons. When user want to find something or browse all records at once, he press a button with grid image, and get all records in grid (a generic form with grid that gets as parameters list of columns to display from alias). After search or browsing, pressing ok in that form will change record in the data form to selected in grid.
2. When you use intensive search and filtering, make 2 or more pages on the form. Forst page with search criteria fields and grid. Second page is a data form for editing. So I can search for records, find record of interest and go to the page for data editing. New record adding just opens data form page.

These are just a samples. You can build your interface as you want. For example, I saw a toolbar-like form docked at left side of main screen, which contained grid displaying list of records from the data edited by current data form. So you can either navigate to required record in grid, or use navigation buttons on data form. Anyway, I do not recommend to use this approach for your case because with filters this approach also will be boring for users - grid is always displayed, so it should work also quickly.

The main point of 2 previous approaches is that user calls grid only when required for navigation/browsing. When editing data, there is no slow down issues because filtering. In addition, with few records it is ok to press 3-4 times the next button. Whenuser works with the same data every day, user knows what data there are expected, usually.