Format Form like Report

No, not unless I see the db.

Anyway, I think you you should rethink your design idea because a report is meant to present data in a meaningful manner whereas a form is for keying in data. If a form looks like a report I think your users will get confused and I don't see the benefit of this approach.
 
understandable, The idea was that the form looks like the report because the report will get printed and updated by employees on the floor (on the paper). The person in the office would update the data which would be easier to update if the screen matched the data changes from the paper.

I'll PM you a link to my database on my OneDrive!
 
Ok, but it doesn't need to be repeated like you have it on the report.
If you have navigation buttons at the bottom of form and a search field, the user can easily navigate to the record they wish to amend, make the amendments and re-generate the report

You could have three or four subforms simulating a group.
 
I believe I sent a message, not 100% sure though... my sent box still shows 0 items :o
 
I got it and I am looking at it, but it will be later tonight for me to respond.
 
Yes I got it.

I'm still going to go back to my former suggestion, main form (i.e. Single Form view) will hold the work orders and everything else goes into a subform. You can create 13 subforms (1 for each ShopProcess) and each of these 13 subforms will house another subform linked to the other tables. That's the only way it can be done.

I still think you're overcomplicating matters because (as previously mentioned) if you create proper search features and navigation controls your users will be fine.
 
I got a form approved that uses a tab control, I'll add the file to the OneDrive. My only problem is that when a tab is highlighted the form scrolls so the tab isn't visible. Is there a fix for this?
 
I won't have time to open your db.

Show us a screenshot instead.
 
Thanks for the file, that helps. The main problem I was having in understanding your structure was semantics--everything had 'Task' or 'WO' in it. I couldn't see how they were distinct from each other or at what level a field went with your data.

This may seem pedantic and unneccesary to you since you understand what each table\field represents, but I would recommend distinct words for your tables\fields. I would model it after how you initially described your problem to us (WorkOrders=WorkOrder, Parts=WOTasks, Processes=TaskOrder, Shops=ShopProcess). Work Orders have parts and parts get processed.

From the looks of things, TaskComplete is a 1-1 relationship with TaskOrder, right? One TaskOrderID in TaskOrder will have at most 1 record in TaskComplete. If that's the case TaskComplete is unnecessary. You should instead put its fields in Task Order--and honestly, it really only has 2 fields (Employee and Comp Date), the rest are duplicates of data TaskOrder already has access to.

Ultimately, your form is going to be sort of a walkthrough system--its not going to be on one page. You would have a WorkOrder form with a subform for WoTasks(Parts). Next to each record in that WOTasks subform would be a button, you click the button and you go to a form based on WOTasks (showing just the WOTask you clicked) with a subform with TaskOrder(Processes) data associated with that WOTask.

I think you do need to work on your structure first though.
 
This may seem pedantic and unneccesary to you since you understand what each table\field represents, but I would recommend distinct words for your tables\fields. I would model it after how you initially described your problem to us (WorkOrders=WorkOrder, Parts=WOTasks, Processes=TaskOrder, Shops=ShopProcess). Work Orders have parts and parts get processed.

From the looks of things, TaskComplete is a 1-1 relationship with TaskOrder, right? One TaskOrderID in TaskOrder will have at most 1 record in TaskComplete. If that's the case TaskComplete is unnecessary. You should instead put its fields in Task Order--and honestly, it really only has 2 fields (Employee and Comp Date), the rest are duplicates of data TaskOrder already has access to.

Been meaning to do this for a few days. Will likely get to it on the weekend (I'm responsible for maintaining inventory for the different shops so much of my work day is spent there)

Ultimately, your form is going to be sort of a walkthrough system--its not going to be on one page. You would have a WorkOrder form with a subform for WoTasks(Parts). Next to each record in that WOTasks subform would be a button, you click the button and you go to a form based on WOTasks (showing just the WOTask you clicked) with a subform with TaskOrder(Processes) data associated with that WOTask.

I think you do need to work on your structure first though.

I have a form that functions similar to this (WorkOrderEntry) and the view this accomplishes is mostly only useful for the initial entering of data/revising how a part is made. The form I am working on (and have found a decent solution for) gives an overview of what needs to be done at each shop process. So the data goes as follows:
WorkOrder -> Shop -> Part. This lets the project managers see what/where everything needs to be completed and gives them an easy view to revise how the work order is being managed. The form below accomplishes this for the most part (although it will keep being revised as it is used and new ideas are created).

sbrgao.png


The last form is used to update the data after the employees complete processes (yet to be created). The employees receive a report that shows all the work orders and processes that must be completed in the process they work in. To maximize efficiency of transferring this data the form should show all the work orders that have at least 1 part that is used in the process. By clicking on the work order number (or a button) a subform should open that shows just the parts corresponded with the process and the workorder.

I have two questions for creating this:

1) How can i filter to show that a work order is related to a specific process? And how can I stop duplicate values?
2) How do you create a button that will filter to show the values described above?

Thanks a bunch guys... You've been a lot of help!

mango97

Edit:

I have a question for reports, and I figure you guys may know the answer.. What values do I pass into the "filter" property (located in the data tab) in order to filter out different values?
 
Last edited:
Both your questions are issues you should tackle after fixing your structure. What you are asking for in both those questions is a navigation/search system for your data. When I have built systems that have complex underlying table structures I first built a query to join all my data together and show all the fields I wanted to let my users search on.

Then I built a form on that query along with unbound input boxes at the top of it. They'd input data into those boxes and then the search form would filter to meet those criteria. Besides each record would be a button that when clicked would take the user to the appropriate form to edit data. That's how you should handle searching. I really think you are trying to kill all your birds with one form and it's just not the best way.
 
All seems logical to me...

I've been working on fixing my back end and have gotten stuck working on an AfterUpdate macro. The macro should update the next task to appear as ready once a value is entered into the CompDate field. Here is a screenshot of the macro:

11iegpx.png


Link to Larger Image

The macro runs fine until I search for the next CalcTaskNum. Originally I was searching with the criteria: "[TaskOrder].[CalcTaskNum]=[TaskOrder].[CalcTaskNum] + 0.01" but this wasn't working, so I've tried using a local variable (am I doing that correctly?).

Regardless, it doesn't work! Any ideas?
 
Sorry, I don't know what you are attempting to do, and I'm not that well versed in macros. I do know that your initial criteria:


[TaskOrder].[CalcTaskNum]=[TaskOrder].[CalcTaskNum] + 0.01

Will never evaluate true. Restate it mathematically:

x = x + .01

There exists no number x such that if you add .01 to it that it equals its original value.
 
I moved the fields in Task Complete to the Task Order table. When a value is entered into the [CompDate] field a macro (or something) must run that determines what the next task is (same part, next task number).

Before this code would work because it would communicate via 2 fields, however I'm not sure how to get it to work in a single table!
 
ok, so that can find the next task. How would that set the [Ready] field to Yes? Or, how can I use that to highlight when the next task is ready?
 
Last edited:
What does [Ready] designate? From your question it sounds calculated. If so, you would calculate it and not store it.

How does it get set?
 
When a task is "Ready" it means that the previous tasks have been complete. So what I was previously doing was having a macro run that after a task was designated as complete it would find the next task and set its [Ready] field to yes.

It's only real use is for conditional formatting. When a record is denoted as ready it is highlighted green on the report/forms.
 
Since the number will repeat themselves for each part how would I make sure that the correct part is referenced?

This is what I have so far,

Before: DCount("TOrderNum","TaskOrder","[TOrderNum] <" & [TOrderNum] And [PartsFID]=[PartsFID])

I followed your earlier advice and have changed some fields to make more sense (i was also having trouble with it).

WoTasksID is now PartsID
WoTaskNumber is now Part Number
WoTasksFID is now PartsFID
TaskNumber is now TOrderNum
CalcTaskNum is now Task#
 
Last edited:

Users who are viewing this thread

Back
Top Bottom