>>>>I think a good tip too is don't overdo it on indexes. I have seen some aps with 20 tags of more on some of the files... This actually causes more network traffic espessially with rushmore turnd on. Generally two indexs, a PK and a Candidate Key should be adequate. Other than that, use more order by and client side indexes.
>>>>
>>>>BOb
>>>
>>>What do you mean by your last sentence? Do you mean "SET ORDER TO"? Don't you have to have an index for that? What are "client side indexes"?
>>>
>>>Thanks,
>>>
>>>Michelle
>>
>>No... "Order By" clause in your views and/or queries. You can also create an index on a view or cursor made read-write.
>>
>>BOb
>
>Oh, views, ok. I thought this was something for tables. I realize that views are supposed to be a good thing, but I find them to be a real PITA. I'm starting to have second thoughts about using them with my project manager app.
>
>Thanks,
>
>Michelle

If I were developing strictly for local tables, I would use a mixture of tables, views and querys. Tables for parent, Views for Child, queries for lookups and validation.

Views aren't that bad once you get used to them, and if you learn a few tricks they are actually quite nice.

BOb