By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
435,619 Members | 1,534 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 435,619 IT Pros & Developers. It's quick & easy.

Check off Items in Form

P: n/a
Hello,

I have a form that users type in a part number and a due date. I then run a
report that prints the part number, the components needed and the processes
needed. For example:

------User Form-------

Part 1 6/25/05
Part 2 6/28/05
Part 3 7/1/05
---------Report--------

Part 1 6/25/05

Component 1--------SAW-----WELD------SMOOTH
Component 2--------WELD-----PAINT
-------------------------------------------------------------
Part 2 6/28/05

Component 1--------DRILL-------WELD
Component 2--------SMOOTH-----PAINT
-------------------------------------------------------------
Part 3 7/1/05

Component 1--------DRILL-----PUNCH
Component 2--------CUT-------PAINT
-------------------------------------------------------------
What the users want the ability to check off (and make dissappear) the
processes each day, so they can see what processes are left.

For example, after day 1 with SAW and WELD done:

Part 1 6/25/05

Component 1--------WELD------SMOOTH
Component 2--------PAINT

I'm confused about how to go about this. I don't want the users to have to
manually type in anything. I want the components and processes to show up
when they type in the part number. I want the user to be able to check off
processes as they go, but I want all the processes to show up when they type
a new part in the form. I would appreciate it if someone would point me in
the right direction.

Thank You,

Chad
Nov 13 '05 #1
Share this Question
Share on Google+
4 Replies


P: n/a
What if you were to insert all of these records into an existing table
with a Y/N field for "completed" or whatever. Or a datestamp for
completed, and then you could just filter for Completed=False or
CompletionDate IS NULL or whatever.

The rest looks fairly straightforward:
for each component, there are a series of processes, which begin X days
from starting date. You can do all that with DateAdd() and calculate
on the fly, and/or insert into a final table.

Nov 13 '05 #2

P: n/a
Hello,

Thanks for responding. Let me see if I am on the right track. I have 2
tables-The first is the table the user types in the part number, contract
(forgot to mention that), and due date. The second has all the parts and
their components and processes:

Part------Component-----Process1------Process2-----Process3
-------------------------------------------------------------------
Part 1----1st component--SAW---------PAINT
Part 1----2nd component---DRILL-----SAND---------PAINT

I ran an append query to pull the proper components and processes from the
above table and add them to a cumulative table. This is the table the user
can edit because it is tied to a specific contract number and the original
remains untouched. I have a form and subform linked by contract number. Am
I close? If so, is there a way to stop duplicate records from being
inserted into this table---the cumulative destination table. If I am way
off, let me know. This is unlike anything I have done with Access. I
appreciate the help.

Thanks,

Chad

<pi********@hotmail.com> wrote in message
news:11**********************@g47g2000cwa.googlegr oups.com...
What if you were to insert all of these records into an existing table
with a Y/N field for "completed" or whatever. Or a datestamp for
completed, and then you could just filter for Completed=False or
CompletionDate IS NULL or whatever.

The rest looks fairly straightforward:
for each component, there are a series of processes, which begin X days
from starting date. You can do all that with DateAdd() and calculate
on the fly, and/or insert into a final table.

Nov 13 '05 #3

P: n/a
Just to clarify my unique values question-The processes will be different
than the parts table if the user changes them, but they will still have the
same contract number. I might get double the component parts needed. I am
using the user input table in the query--if I have 5 records and add a
sixth, I don't want to append the original 5 again. I didn't explain very
well, but I really appreciate the help. Again, I might be way off from what
you suggested.

This will be a list I keep adding to. In addition, I will add a check box
for Total Item Completed, so I can filter out an order (not just processes)
when completely done.

Thank You,

Chad
<pi********@hotmail.com> wrote in message
news:11**********************@g47g2000cwa.googlegr oups.com...
What if you were to insert all of these records into an existing table
with a Y/N field for "completed" or whatever. Or a datestamp for
completed, and then you could just filter for Completed=False or
CompletionDate IS NULL or whatever.

The rest looks fairly straightforward:
for each component, there are a series of processes, which begin X days
from starting date. You can do all that with DateAdd() and calculate
on the fly, and/or insert into a final table.

Nov 13 '05 #4

P: n/a
I got it. Please disregard the other posts. Thanks a lot for the help. I
really appreciate it.

Chad

<pi********@hotmail.com> wrote in message
news:11**********************@g47g2000cwa.googlegr oups.com...
What if you were to insert all of these records into an existing table
with a Y/N field for "completed" or whatever. Or a datestamp for
completed, and then you could just filter for Completed=False or
CompletionDate IS NULL or whatever.

The rest looks fairly straightforward:
for each component, there are a series of processes, which begin X days
from starting date. You can do all that with DateAdd() and calculate
on the fly, and/or insert into a final table.

Nov 13 '05 #5

This discussion thread is closed

Replies have been disabled for this discussion.