Hi
Can you give a full detailed explanation what the database is all about?
What process are you trying to record?
Hi
Can you give a full detailed explanation what the database is all about?
What process are you trying to record?
You can PM me if you need further help.
Good Reading https://docs.microsoft.com/en-gb/off...on-description
You had the ? thing in the code window, not the immediate window. When you're presented with a term you don't understand, Googling it is better than either not bothering to figure it out or coming back here to ask, because that shows initiative on your part.
Took me about 30 minutes just to resize everything so that the scrolling between forms and application window didn't drive me nuts. It's way too big for my laptop.
Anyway, good that you posted the db. Here's a point that needs to be considered - subforms load before main form, so if you ever figured out how to determine the hierarchy, you probably would have put the code on the form you wanted to affect, which would open first and would not find the name of the parent form because it would not be open yet (if you used the hierarchy that you figured out). To get around that, you would use Me.DataEntry = true in the subform (e.g. Project Info) open event. However, it would always open that way and you'd never see existing records unless you worked around that.
So you could put Forms![User Input].[Project Information].Form.DataEntry = True in the Open event of [User Input] form and it will switch that subform to data entry mode. You could open the main form then load the subforms when user clicks on the page as mentioned, but your form opens fast the way it is. However, it would be easier/better to set the data entry mode on the opening subform when the page is clicked, otherwise you need to add additional lines like the one above so as to do this on every subform if that's what you need. Doing so will prevent you from being able to open one subform as data entry and another subform in some other way. It might be wiser to open the form as data entry only when the form is opened by itself and not on a page.
In the end, I think your original question is now answered, but whether or not you have the right approach is another topic. If you're redesigning because of other things you're researching, then consider whether or not this approach is the best. To advise on that would require more understanding of what the process is, I think.
Last edited by Micron; 01-07-2022 at 03:11 PM. Reason: numerous changes
The more we hear silence, the more we begin to think about our value in this universe.
Paraphrase of Professor Brian Cox.
So it is a project dashboard in a way. It is r really for the project manager to use to manage their project but more of a way for us to present all the project we have going on and what their status is. It is a corporate “tool” that we are required to track most of the data. Some of it is site specific. Essentially a database that at anytime we can pull up and show what projects are on going and what the status is. Overall though the plan is to pull it into powerbi for a more visual display. It isn’t probably the most efficient thing but to a certain degree we only have so much wiggle room.
So the fields are mostly common fields.
Project number name and dead
Project team members.
Spending information schedule milestones.
And then lots of checklist and risk Assessments numbers and then results. Right now the database has around 200 rows.
I should add that I am making this update to get away from excel and also to make it
More user friendly to add and update information compared to how it was in excel.
Last edited by petro62; 01-07-2022 at 06:21 PM. Reason: More detail
Hi
Not knowing your business it is very difficult to interpret what your table fields represent.
Can you give us an explanation of the following field names:-
CM EWP PQ MCP RnDCheck ProMan ProCon ProTech ProStart ProZO PerAssigned Actual PerInvoiced Committed Feasability Conceptual Definition Design Construct Startup ORA Process LOTO Calib Visual PMs SIMTWW AMcomp SafetyMap SUC MRAops MRAdel PRrisk EWPdel MCPper GPRM2tar GPRM2act GPRM2met SPRper SmallPR SmallMCP PRtar PRact PRmet SOPmet ETCmet Qualitymet HSEmet HSEInc SPCend
You can PM me if you need further help.
Good Reading https://docs.microsoft.com/en-gb/off...on-description
I answered as best I can. I can’t fully detail something’s so I apologize if it doesn’t really help. Now that I look at it closer I kept the order of things the same as the original sheet but I think there is some reordering that I could do to help group things a bit better.Hi
Not knowing your business it is very difficult to interpret what your table fields represent.
Can you give us an explanation of the following field names:-
CM is a change management number EWP this is a checklist and this is just asking if it is required PQ is asking if validation is required MCP asking if another checklist is required RnDCheck asking if another checklist is required ProMan project manager ProCon construction manager ProTech technical engineer ProStart start-up leader ProZO operations zone owner PerAssigned percentage of budget assigned. Actual amount of money invoices PerInvoiced percentage of assigned that has been invoiced Committed how much money has been committed so far Feasability a schedule milestone Conceptual a schedule milestone Definition a schedule milestone Design schedule milestone Construct schedule milestone Startup schedule milestone ORA was this checklist completed Process we’re these directions written LOTO was lockout tagout completed Calib we’re calibration forms completed Visual we’re visual controls completed PMs were PMs written SIMTWW were simtww written AMcomp was this work complete SafetyMap was a safety map made SUC was a step up card updated/created MRAops checklist percentage MRAdel another checklist percentage PRrisk checklist percentage EWPdel checklist percentage MCPper checklist percentage GPRM2tar target reliability at 2 months GPRM2act actual reliability at 2 months GPRM2met was target met SPRper checklist for smaller projects SmallPR checklist for smaller projects SmallMCP checklist for smaller projects PRtar month 1 reliabilityTarget PRact month 1 actual reliability PRmet was target met SOPmet was start of production date met ETCmet was budget met Qualitymet was all quality criteria met HSEmet was HS&E criteria met HSEInc # of safety incidents SPCend small project checklist final
Your 1 x Projects table needs to be broken down into your business process.
If you take for example the process of a Customer can Order 1 or more Items.
To record this process we need tables to deal with each part of the process.
tblCustomer
tblOrders
tblOrderItems
Looking at your Projects table can you attempt to map out what happens after you
enter data into a table called tblProjects with only the following fields:-
All of the other fields are related to 1 project only and will need to be entered into a related table.
ProjectID ProjNumber ProjName ProjDesc ProjStatusID ProjAreaID ProjTypeID
You can PM me if you need further help.
Good Reading https://docs.microsoft.com/en-gb/off...on-description
So essentially make a table with the project information. And then another table with the project team then table for schedule and so on? And they are all join by the keyid?
Hi
Take a look at the attached.
I have created a table to deal with :-
Project
Project Details
& Project Milestones
Look at the relationship diagram and then look at how the Forms are constructed.
You can PM me if you need further help.
Good Reading https://docs.microsoft.com/en-gb/off...on-description
Just got time to take a look at it. Thanks for this. I know some of this probably has to do with normalization which I still don't fully understand, but I understand some of the big tables (Projects,Milestones, ProjectDetails), but why the single table for just Phase. I am just trying to understand what that helps with so for future things I can understand how to break them down better. Thanks again this will give me a lot to look through this weekend.
Hi
tblPhase contains a list of all the different Phases you use for Projects.
This then makes it easier for the Data Input on the Form as you just create a Combobox to lookup the List of Phases. It saves on typing as well.
You can PM me if you need further help.
Good Reading https://docs.microsoft.com/en-gb/off...on-description
Let's not forget that lookup tables (not lookup fields in tables) alsoThis then makes it easier for the Data Input on the Form as you just create a Combobox to lookup the List of Phases. It saves on typing as well.
- control data input; users can only choose values from the table, preventing simple spelling mistakes
- support accurate record retrieval (see point above for why)
- properly used, the numeric PK field of the lookup table becomes the data in the related table (Projects?) so that if the lookup value ever changes (e.g. "Filed" becomes "Archived"), nothing needs to be done. Otherwise, an update has to be propagated everywhere.
The more we hear silence, the more we begin to think about our value in this universe.
Paraphrase of Professor Brian Cox.
So I want to make sure I understand how this works. I see how everything is connected through the relationships, but I just wanted to make sure I am getting this right. So for instance lets take project type. You created a table that sets an ID to each type of project. frmProjects has the combobox which pull up the list of project types from tblProjTypes.... I guess I am just getting myself lost trying to trace the process. I am sure it is simple an in front of my face, but some reason it eludes me. Would you be willing to walk me through how the process works so maybe the light bulb will finally go off in my head?
bit late to the party re cross posting. But at the time of writing this post there are 1006 viewers on this site. Of these, only 9 are members (the rest are guests and cannot post questions) and of the 9, just 6 are what I would call regular responders. Of those 6, I know 5 are regular responders on at least one other access forum. A quick look at the other forums I am involved with show similar ratios at this point in time. Just want to point out that the (regular) responder community is pretty small so 'time wasted' is spread across a relatively low number of individuals. Not having a go - you weren't to know. But now you know. No problem with cross posting per se, so long as you provide the link.
You can see this forum information at the bottom of this link https://www.accessforums.net/index.php
Yes I understand this now after @Micron informed me. It is good to see the numbers you posted though. I didn't realize it was that small of a group.
Hi
To explain the process in a little more detail.
I created a Form called frmProjects based on the tblProjects.
Then I switch the view to Design View
I then followed the Steps detailed in the attached Word Document.
You can PM me if you need further help.
Good Reading https://docs.microsoft.com/en-gb/off...on-description