Hi, Erik,
So, what is the point to have one view for viewing and one for updating? Think about it. My understanding is that views suppose to be more convensional way to gather data from different sources(tables) and allow program to manipulate data in such tables. "Something is ratten in Datch kingdom..."(:-)
I asked the same question on this forum awhile ago. I'd like to learn more about views and be fluent on them. Could you, please, suggest something in my case?
I have database where user suppose to enter new doctors practicing in some geographical area. I have three tables in database to keep data about them: Specialty, Doctors and Offices. All tables have foreign keys as a primary to identify each record. Their structure as follows:
1. Specialty: spec_id(i),spesialty c(10)
2. Doctors: doc_id(i),spec_id(i),off_id(i),...
3. Offices off_id(i),doc_id(i)...
As you can see by doc_id it is possible to identify doctor and his specialty with all locations where this doctor practicing. Relationships:
Specialty->Doctors(1-to-many)->Offices(1-to-many)
I've tried to create a view for data entry without any success. Data entry form suppose to allow new records in all files... Finally, I've give up and have my form based directly on tables (of course, buffering enabled and cancel allow you to rollback...)
Any thoughts?
Thanks for your attension for this problem.
Best regards