>Hi Hilmar,
>
>Thanks for your reply.
>You mentioned using views instead of tables. Currently, I do not do this. Your example is very similar to my situation. The employee
>table is related to the child claim table which has thousands of records. My reports seem to go pretty good, it is mostly the data entry
>forms, saving data, and viewing data which is sluggish (which is most of the system).
>
>I will start reading up on VIEWS today and learn more about them.
>
>Thanks again.
>
>Fred
A view is basically like a cursor, except that it is R/W.
It is important to specify the PK correctly, or else, perhaps, when you intend to update a single record, you actually update several.
There is a very important option in the view designer, "Send updates"; if this is not marked, all other update options are ignored!
For showing the view for different sets of child data, please see help under "Requery()".
Hilmar.
Difference in opinions hath cost many millions of lives: for instance, whether flesh be bread, or bread be flesh; whether whistling be a vice or a virtue; whether it be better to kiss a post, or throw it into the fire... (from Gulliver's Travels)
