Recent content by MikeFar

If I were you, I would do a one to many relationship with one table having an appt ID as PK, date and test ID, then create a 1 to many from from that table to another table having all the tests in it. Each test ID would have the test details, result, date of result, consultant, value etc. A...

As regards to different users, why not split the database any make different front ends depending on their personal preference? Regarding the second problem, I would create 2 forms with identical combos, text boxes etc but with a different view. Than just make a macro to close one and open the...

I will take your advice and try again with the one to one. Re SQL I am still far off. I can hardly convert Macros to VB at this stage. In fact I tried it and I had to go back to Macros! Still, it will be a 40-50 field table.

True. 1) I changed it to a many to many following advice from this Forum. It was nor like that in my version 1! 2) Drugs and Medical conditions are probably easy to identify as Many 2 many...with experience. The fields in the long list will probably have to remain in the PtDetails table as...

I fully agree with what you said but as I said in my post, forget the dates etc, this is just a report to survey the condition of all the parts. Parts which are broken, scratched, missing, cracked, rusted...all will have an entry beside them. Parts which are ok, will be skipped. Imagine a...

Say I turn the question 180 degrees so non medical people can understand better. If a car mechanic wants to print a report on each car he has in his garage for surveying purposes. He makes a one table database with car reg. no, chassis number, engine number and a list of parts like front bumper...

Ok. The numbers are actually the names of the teeth! I tried making different arrangements but that was the only one that worked so the dentist can tick which tooth is present and which is not. Each tick box corresponds to one particular field. On the consent table, each field supplies info to...

1) The drugs are just a list of medications each patient is on. So it is related to Patient ID and more can be added if the patient turns up and tells the doctor that he is on some new drugs. It's purpose is just to know what treatment can be given and which cannot. 2) The database is not...

This is how it is now. Unfortunately, it has plenty of jargon which might not make sense to most people. It is actually planned for a dental clinic so besides the medical aspect, there has to be information about each tooth, occlusion, defects etc. I am open to all suggestions as this my first...

While writing the previous post, I realized that I could put all the numerical parts in another table. I copied the original table (with Data) to a new table, linked it, removed the duplicates, new query ....and it works. Are 40 fields still too much??? I cannot figure out how I can group more...

I did! The remaining ones (about 70) would require an entry such as a short description. They are not yes or no items. About 30 of them are mesurements of different parts of the anatomy. So I have the name of the anatomical part and a text box to enter the value. It was close to 220 fields when...

Done at last! Is a table with 99 fields considered as too large? About 70 of these fields are set as not required and will only be populated in about 1 in 4 records. Will all those blank fields bloat my database?

I am trying to do as you said. Incidentally, yesterday I came across a similar reply and an example is also posted. (Search allenbrowne casu-23) Somehow, I cannot get the child data to link with the parent. I will have another go this evening. Interestingly, this guy suggests that Tick box...

The conditions table may have 5 or 6 different options per condition. Eg: Mild, moderate, severe, acute ....and I have drop down menus for those. The thing is that now I have right mouse clicked the joins and deleted the relationships for medications and conditions. Since they have the Primary...

Each Patient may be taking 5 or 6 different medications and be suffering from a number of health conditions. If I create a 1 to many table, I would only be able to select one medication and one condition! Adding a medication or condition is easy. Just add a field in the table, view field list...