Recent content by GaP42

The cost is not to government .. everyone bears the cost ultimately, and the cost may not just be monetary. Failures associated with using different measurement systems have cost lives. Maintain the rage Uncle!

DickyP - notice I was not converting between imperial and metric - it was about conversion between units within one system or the other, not converting units between systems (which does cut both ways when one has to do it). The conversion argument as shown still stands, and so is not sophistry...

Like you I also began with imperial measures and coinage and experienced the change to metric, and from my perspective, it wins hands down. Just take your chery picked measurement - 32.5 inches - how many feet is that? what fraction of a yard? in metric 825.5mm is simply converted to cm, m etc...

If your database is to support multiple clubs simultaneously then you would also introduce a ClubId for members and Posts, and a club table. Practical uses: that is dependent upon your club needs. Can be extended to manage attendance records at monthly management meetings (a schedule), that can...

Hopefully the relationship diagram is a simplification of what you actually have - specifically "Table1" - as it has some serious structural issues as mentioned in #10. @MajP has provided advice on getting the combo box to work correctly - as a simple 2 item list of InjuryPK and...

You may consider some restructuring of your data: You have basic patient data (DoB, Gender - age is calculated and should not be stored). You then have data that varies for that patient depending upon the interaction: Referral Reason - multiple referrals may occur over time - suggesting a...

As @Gasman indicates, the use of a subform which allows selection of a Nature of Injury Classification value (using a drop down list box / search) to populate the NatureofInjury table associated to the patient record from the main form would be appropriate.

Generally a nature of injury field would be free text, given that there is so much that can be described in that context ( body location, severity, ...), however you may apply a classification - for example based on applicable SNOMED items (if this scheme is available to you). I would advocate...

Difficult to advise with the outline provided so far. 1. The "calculation" query is run hourly, the report daily (collating the hourly calculations)? Why would the query not be run daily too, with data filtered to each hour for the purposes of calculation, or do some rely on previous week...

Conceptually, from your Table Relationships, the Weight_Main table is a "job" table. A job may be the subject of many weighings. The Weight_Id PK / FK name is somewhat misleading and may then be more appropriate named as Job-ID or equivalent. You indicated some concern that the record may be...

I agree @ebs17 - a Specialist may be perform/ be engaged in multiple Specialties, and a Specialty may be performed by / engage multiple Specialists. The conceptualisation of the form I would presume needs to establish the records of Specialist to Specialty, with an isActive attribute (as a minimum).

Arthur C Clarke - Any sufficiently advanced technology is indistinguishable from magic.

Just in the interests of avoiding misconceptions: 1. Energy is not associated with the speed of electrons around a nucleus: as electrons move in orbits their motion is described as acceleration, and so, as for any object that experiences acceleration, a force is being applied and the energy...

The No - I do not think so: you have a simple workflow ... someone submits a record/proposal, another reviews and approves the record. If your workflow is never to be extended to more levels then you may structure it as one core table with fields for capturing the needed details and with...

Shakespeare was such a disruptive influence then :)