Forum Discussion
Vere_Nicolson
Aug 09, 2023Copper Contributor
Binary master and Date child fields,
I have a database for animals in a zoo. Animal ID information (and lifelong data which won't change) is in an ID table. (Tbl_PC_Animal_ID) During its life each animal may have one or more health iss...
Vere_Nicolson1995
Copper Contributor
Thank you for replying, many of your criticisms are valid and others are because I didn't explain things fully in an effort to keep my post short.
The table of medications (TblRx) has the following fields. ;
Rx Key(Home key) Issue Key (which links to a list of health problems which in turn links back to the animals ID) Start date, Drug, Route, Frequency, Finish date, Comment, Follow up action, follow up date, follow up completed.
Each record in TlbRx is essentially a prescription, or recommended course of one drug supplied by me as veterinarian. This way has served me well for years but I saw the verification of delivery as a separate function that did require daily records, and would need to be entered by staff.
At my previous position the delivery of medications was recorded by veterinary nurses on paper, (you sometimes have to let people do things their way).
My current zoo is smaller so I was going to include the recording of the drug administration in the database, and yes, initials of the administering staff member, or at least the staff member doing data entry would be a good idea. I will include that in the verification table which will now have the following fields; CheckOffRxKey, (Home key) RxKey, (to link to Rx table) RxDate, RxCheckOff, Initials.
I think I can resolve this if I can get the typed-in-date/Qry expression to be data type date instead of a binary. Alternatively there may be a better approach.
Thanks again for your reply.
The table of medications (TblRx) has the following fields. ;
Rx Key(Home key) Issue Key (which links to a list of health problems which in turn links back to the animals ID) Start date, Drug, Route, Frequency, Finish date, Comment, Follow up action, follow up date, follow up completed.
Each record in TlbRx is essentially a prescription, or recommended course of one drug supplied by me as veterinarian. This way has served me well for years but I saw the verification of delivery as a separate function that did require daily records, and would need to be entered by staff.
At my previous position the delivery of medications was recorded by veterinary nurses on paper, (you sometimes have to let people do things their way).
My current zoo is smaller so I was going to include the recording of the drug administration in the database, and yes, initials of the administering staff member, or at least the staff member doing data entry would be a good idea. I will include that in the verification table which will now have the following fields; CheckOffRxKey, (Home key) RxKey, (to link to Rx table) RxDate, RxCheckOff, Initials.
I think I can resolve this if I can get the typed-in-date/Qry expression to be data type date instead of a binary. Alternatively there may be a better approach.
Thanks again for your reply.
Tom_van_Stiphout
Aug 10, 2023Steel Contributor
You wrote earlier:
> That date is held in expression1as a binary. I can't make this other than a binary. (or if I can please let me know how)
This is *very* strange. Can you post expression1?
In general the best course of action is starting with a correct database design, then build expressions and more complexity on top of that, not compromising db design for an unruly expression. I think together we can slay this one.
Another thought about speeding up data entry: would it help to have barcodes for animals, employees, and medications? Then entering a record is mostly zapping some barcodes.
> That date is held in expression1as a binary. I can't make this other than a binary. (or if I can please let me know how)
This is *very* strange. Can you post expression1?
In general the best course of action is starting with a correct database design, then build expressions and more complexity on top of that, not compromising db design for an unruly expression. I think together we can slay this one.
Another thought about speeding up data entry: would it help to have barcodes for animals, employees, and medications? Then entering a record is mostly zapping some barcodes.