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

Dynmaic input in form

P: n/a
I have a table with two columns, ItemName & ItemSubCategory. Below is
an example of the entries:

ItemName ItemSubCategory
Transfer Manual - A
Transfer Manual - AE
Transfer Manual - E
Transfer Manual - G
Transfer Manual - I
Transfer Manual - M
Transfer Manual - R
Transfer Manual - Ro
Transfer Manual - U

I have a form with a combo box, if the user selects "Transfer", then
another form pops in front.
What I want this form to do is to always show the following fields for
input:

[Date] Manual - A [# Completed]
[Date] Manual - AE [# Completed]
[Date] Manual - E [# Completed]
[Date] Manual - G [# Completed]
[Date] Manual - I [# Completed]
[Date] Manual - M [# Completed]
[Date] Manual - R [# Completed]
[Date] Manual - Ro [# Completed]
[Date] Manual - U [# Completed]

*[Date] Default = Date()

However, I want these fields to be dynamic. So, if I add "Manual - X"
to the table it will then add "Date Manual - X [#
Completed]"

I am not sure if this can be done. Any suggestions would be greatly
appreciated.

Apr 26 '06 #1
Share this Question
Share on Google+
1 Reply


P: n/a
A better idea of what was then going to happen would help.

On the surface it would seem that another child table with a FK back to
the table this is all supposed to hang off of would be the route.

We have an application here that has a project, and for every project
there is a defined set of tasks. When the project is created, we run an
append query that adds records to the table for every task and its
scheduled date. The append query reads a master subtask table that
contains the task description, and days to add to the start date for
each task. That way when they changed the task description or added new
tasks the the standard it created what was needed for all new records.
(Word of warning... Because of the way they wanted reporting done, if
they added new master tasks, we had to create dummy completed entries
for all prior projects that did not originally have those tasks. Not
difficult but took some cogitating.

Hope this gives you some ideas.

Ron

Apr 26 '06 #2

This discussion thread is closed

Replies have been disabled for this discussion.