>>>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
>
>They're nice in principal, but I find them to be more error prone. Maybe I should phrase that better... It's not so much that the views have errors, but that there's much more potential for me to screw up with them. Like with surragate keys. I thought I was all set because I use the default value of the field to fill in a sequential key automatically. Then I started using views and had all sorts of update conflicts. I finally traced it to the fact that the view doesn't get the key until it updates the table. So I had to go into all my inserts and explicitly tell it to get the key right away. Stuff like that has really turned me off them, but I use them anyway just because they do things better than cursors.
>
>Michelle

You can set the deafault value on the view's field too. You may loose a few keys that way, but you don't have to worry about saving the record to get the FK for a child file. And you wont have to populate them manually.

BOb