Search results

Lets see if I am getting this right. Are you saying to rename the existing t_PeriooperativeData to t_OperativeData and retain all the current fields, and add a field to hold the values Pre, Inter, Post ? Would this necessitate a new table t_OperativeValue containing the mentioned values?

I will revert back to what we started with and try again? :unsure: The tables are as follows: t_Visit, t_Advanced_Directive, t_DVT_Data, t_PerioperativeData, and t_Temperature_Monitoring These are the main tables.

Here is a pass at your suggestions as I understood them ... queries and forms have not been redone. Tables added and relationships started. Is this a correct path?

I am creating some smaller tables as you have suggested. What is your thought on lookup (lookup wizard) being used in the other tables??

I guess I was confused .... previous post lead me to believe you were suggesting splitting the table. With that said PreOp, interop and post op all have separate tabs in the sub form now??

You suggested that the Perioperative table be split into three sections which I see how to do, but each section is directly related to the first section, Thus a one to one relationship? So I am confused why to break this up??

Okay .... I am now looking at simplifying the tables. While some are quite simple, others posse more questions as to normalization. If tables are in the simplest form it seems data is more fragmented? Some tables are reference tables and others should be tables that hold the data elements. When...

I know have lots of time to work on this, so I would like to be able send this back to both of you in the future. Is this a possibility

This will now be an opportunity to learn as I said .... I am already looking at normalizing and what was missed previously. I get the point of each type being its own sub form with a related query for data retrieval but my question is how does these sub forms work for data entry? and what will...

It would be good to maintain the data in this new database but may not be essential as it is preserved in the current database. t_Perioperative_Data was used because the 3 operative types make up the perioperative data. I see your point that this could be broken down to 3 separate tables and...

As I have said this database is being retired. So now this is a learning opportunity for me. I get the idea of three operative types ... so each type would have its own sub form for data entry, (Option 2) ?

I think I need to explain the why the names were done the way they are? There are three sections; Perioperative, Intraoperative, and Postoperative. The idea was to have a continuous flow or sequence. What you are saying I believe is that the sections could be different tables and have...

Pat, Thank you for your insight and suggestions. I found out last night we will not be continuing with the database!! However I will use this as a tool to learn from. I think using the table analyzer as a starting point maybe useful and looking at how the primary and foreign key relationships...

I appreciate everyone's help!!!!! .. I will await Pat's reply and help

I am very happy to have your assistance!!! 2-3 days is not an issue and I would much prefer to have one point of contact

Having no experience with VBA that option is out. 22 Queries??? I am not sure where I would start. I have watched several videos on forms and sub forms to create this so I am not sure how I created this multiple bound sub forms?? I would appreciate any assistance as this is the last piece to...

Okay ...... at this point I am lost as how to fix this. 1. when this was originally built no one was not aware that number suffixes were a bad thing. Not sure what would happen pulling this to another table 2. what happens when you remove the visit table from the sub queries to the rest of...

Huuummmm ....... frmVisit is the correct form. I am far from and experienced Access user; have had lots of assistance with some of this build. I am a bit lost on what you are trying to tell me??? How would I know where to make the changes? What is confusing is that the data appended into the...

The attached database sample is to be a replacement for one currently in use. All records from the Current database have been imported, the associated queries and reports all function the way they are supposed to. (Validated by comparing reports between the two versions ..... I have only...

I will try to refine ……