Recent content by June7

Option 4: Certainly primary and foreign keys. Each of the 3 operative tables would link to Visit with vid.

So PQ1 and PQ8 and PQ15 each document a different question? Not the same question asked 3 times? If you don't want to fully normalize data structure, options have been provided. Restated: 1. single table and single subform instead of 3 and no code required 2. eliminate columns from table and...

Fields with a number suffix usually indicate repetitive type of data. Example: University1, University2, University3. Are you saying your 3 distinct sections don't document the same kind of data? PQ1 and PQ8 and PQ15 aren't documenting the same thing? What are they documenting? The problem is...

May or may not be contributing to issue but do all the queries use a field named Time? Time is a reserved word and advise not to use reserved words as names. Remove NorthCompressorRoundT.LoggedAt = [LatestCompressorRoundQ]![Time] from WHERE clause because already have these two fields linked in...

Conditional Formatting is far from a temporary solution. With VBA, all records on form will show the same settings so is not practical for continuous or datasheet. On a report, VBA would have to be in Format event which executes only for PrintPreview or direct to printer, not ReportView.

It is but should use Conditional Formatting instead of VBA. Yes, form Current sounds reasonable. Also, each textbox AfterUpdate or LostFocus event.

I am saying that if you follow my design suggestion, renaming the table might make more sense but you decide. I also said you would remove two of the sets of repetitive fields. Instead of a set of fields for preoperative, a set for interoperative, a set for postoperative, there would be only 1...

This is not what I was suggesting. My suggestion did not involve adding any tables (exactly what were the new tables). I suggested a single operative data table (t_Perioperative Data renamed as t_OperativeData) with a single set of operative data fields (not 3 sets) and a new field...

Not sure what I said led you to think that but sorry if I was not clear. You had 3 separate tabs to begin with - that's what suggestion is trying to accommodate. You will still have 3 tabs - PreOp, InterOp, Postop.

What do you mean by 'split into three sections'? I am not suggesting table be split. I am suggesting each form will have filter to only show desired operative type records. You were getting 3 records before but each had a bunch of empty fields. Now there will still be 3 records but without all...

I think datagrid and gridview are associated with other programs such as C#, VB6, VB.net. In Access, use a form in Continuous view. Or a form in Datasheet view and format an unbound textbox to look like a button.

I handle versioning a little differently. Version table is in backend and has one record with version number. Form in frontend has a label with a version number. When frontend opens, this form opens by default and code compares record value with label caption and if different there is a new...

Attach file to post in thread.

Will still use pk/fk link for each form/subform and each subform will create a separate record. Therefore there will still be 3 child records associated with each parent (master) record but since the fields are more normalized, will not be 3 records with lots of empty fields in each. Textbox...

Need a unique identifier field. Autonumber should serve. https://www.access-programmers.co.uk/forums/threads/sequential-numbers-in-a-query.312520/ Review similar threads list at bottom.