25. marts 2002 - 14:24Der er
7 kommentarer og 1 løsning
Sammenkædede tabeller
Jeg har 2 databaser, den ene indeholder oplysninger om patienterne, så som CPR, fornavn, efternavn, adresse osv., den anden indeholder nogle ydelser til de enkelte patienter. patientdatabasen skal bruges til andet og jeg ikke gider at indtaste/opdatere hver gang der kommer nye patienter til, er jeg interesseret i at ydelsesdatabasen er kædedet sammen med patientdatabasen. Der er dog det problem, at hvis jeg for en patients ydelse ændrer CPR nummeret, ændres det også i patiensdatabasen! Ikke lige det jeg ville have den til. Any ideas? (jeg har oprettet en relation mellem den sammenkædede tabel og ydelsestabellen)
I dette særtema ser vi på, hvordan cloud og AI bliver fundamentet for virksomhedernes digitale forretning, og hvordan de nye muligheder for automatisering og forretningsværdi kan udnyttes uden at miste overblik, sikkerhed og menneskelig kontrol.
hi puppetmaster I am not sure I understand the problem! How are your two tables linked, are you using CPR number? What us getting changed in the "ydelse" table, CPR number?
If your tables are normalizes then CPR -number should exist as primary key in (for example) "patient" table and as the foreign key in "ydlese" table.
Why should the CPR number change in the ydlese table, isnt it the same patient????
Terry, I use the formguide to make 3 forms based on the 3 tables that you see in the pic.......(sammenkædede formularer).......the form cprnr is the "top-most" form, the Screeningform is the level below that and the mammografiform is the lowest form (if you know what I mean).........IF I make any changes to the data presented in the cprnr form, the data changes in the related table, which is the "linked table".......I do not want this.........I know I can prevent "dataindtastning" on a per field level in the form.....but the user can STILL open the table and change the data......I thought that when you link to tables outside your database, the "remote" data couldn't be changed.....but they can.....
If I understand you correctly you want to STOP users from alteing data in the CPRnr table which is linked from another database, is that correct? You can make the from read only so that users cant alter data here, but as you say they can alter data directly in the table. You can ensure that the database window isnt displayed and also make you own menu so that they cant open it, but again if they WILL alter data for some reason they will find a way.
I normally make my own menu's and hide the standard menu's and database window, and then make it all into an MDE file. This stops them playing around to some degree.
I see...........but I've never "dabbled" in making my own menues........don't know where to start......you ARE talking about replacing the Files, Edit and so on menues, right?
Tilladte BB-code-tags: [b]fed[/b] [i]kursiv[/i] [u]understreget[/u] Web- og emailadresser omdannes automatisk til links. Der sættes "nofollow" på alle links.
