>has anyone ever written an office library system in visual foxpro? can i get screenshots of the system? i have no idea on how to design the interface. pls help me.
>
>TIA.

For the interface part, I suggest that you use the same basic interface for most of your form.

For example, in Visual Extend (get the demo to see what I mean), the standard form has two pages on a pageframe; one page shows a grid, which allows the user to select a record. There are options for incremental search in any column, sorting on one column or on more than one, and filtering data, among others. All this is programmed in the base classes, in such a way that it is available to all forms.

A special problem are related tables; in Visual Extend, and without too much additional programming, this is best solved with separate forms - one for the parent, and one for the child.

Note that all the above applies to ANY system that access a database; your main design decision, for a specific system (like a library system) is, how to normalize the tables. I don't have any specific experience in a library system; for your purpose, try to figure out what you need, and use normalization rules (simplified explanation in my article at http://www.utmag.com/August2002/Page7.asp ) to decide what tables you need.