Mr. Zonneveld,

Thanks you for your informative reply. The file sizes are OK.

I'm more concerned with the possibilities of corruption. For instance:

Should I plan to use the "update" verb exclusively when storing data from records changed in master file maintenance screens?

Since the normal flow of information does not include multiple people working on the same record can I fearlessly use the "replace" or the "gather memvar" commands?

Do I need to impose locks across all records being updated or does Fox 7.0 and above do that automatically?

In parent/child tables (as in orders and orderitems) what is the quickest slickest Fox way to develop screens that work in tandem to update orders and items?

I ask this because my experiment with the "one to many" option in the form wizzard yields a disappointing result. I know the users cannot leap to deciding wether they should be adding a "parent and a child" or just "adding a child". I'll get hundreds of calls on that if it is even accepted as an application.

What do you do for those kinds of forms?

I appreciate your response.
Bob