form with no datasource- just map to navigate to other forms

[babs]

I have created a map of our plant(small). I would like to click on a
location of the map(just a text box - know how to add event procedure to go
to form- not sure of all the code to put) and have it go to a filtered form
(based on location) for cleaning jobs required in that area. First of all it
is saying not record source. Not sure how to tie these together?

Once it goes to that form I would like the user to add to the jobs required
- datedone and initials. Not sure how to add these to field - do I need to
dump the required jobs into a new table???

Thanks in advance for the help,
Barb

 

[John W. Vinson]

I have created a map of our plant(small). I would like to click on a
location of the map(just a text box - know how to add event procedure to go
to form- not sure of all the code to put) and have it go to a filtered form
(based on location) for cleaning jobs required in that area. First of all it
is saying not record source. Not sure how to tie these together?

Once it goes to that form I would like the user to add to the jobs required
- datedone and initials. Not sure how to add these to field - do I need to
dump the required jobs into a new table???

Thanks in advance for the help,
Barb

I'd suggest using an unbound form with Label controls; a label has a Click
event and can actually be used like a command button.

I have no idea where your required jobs are now, but if you have a table of
Jobs, each of which can be done many times (on different days by different
people), then yes, you need a new table with the JobID, the EmployeeID (I'd
suggest NOT using initials, just in case you have Joe Smith and Jane Salvatore
and Juan Sandoval all on staff) and a date field (defaulting to Date() or to
Now() if you want the date and time done). This table could be edited using a
Subform of the Jobs form.

John W. Vinson [MVP]

 

[babs]

I have no idea where your required jobs are now, but if you have a table of
Jobs, each of which can be done many times (on different days by different
people), then yes, you need a new table with the JobID, the EmployeeID (I'd
suggest NOT using initials, just in case you have Joe Smith and Jane
Salvatore
and Juan Sandoval all on staff) and a date field (defaulting to Date() or to
Now() if you want the date and time done).

Yes, you are right on with the above advice.

Instead of using the mainform/subform suggested below.
This table could be edited using a
Subform of the Jobs form.
I would like ALL of the jobs listed for that given day of the week to show
at ONE time- not just one record - on main and many in the sub for the
initials and datedone. I would like ALL jobs required for that area on that
given day to be listed on ONE sheet - there are not they many-they could fit-
and allow for the initials(or employeeid) and datedone be able to be INPUT on
each visible job on that ONE screen???? Not sure how to set up if not
Mainform-subform.(the one to many display)

Thanks again,
Barb

 

[John W. Vinson]

I would like ALL of the jobs listed for that given day of the week to show
at ONE time- not just one record - on main and many in the sub for the
initials and datedone. I would like ALL jobs required for that area on that
given day to be listed on ONE sheet - there are not they many-they could fit-
and allow for the initials(or employeeid) and datedone be able to be INPUT on
each visible job on that ONE screen???? Not sure how to set up if not
Mainform-subform.(the one to many display)

Well? By all means, use a mainform (with the date) with a continuous subform.

John W. Vinson [MVP]