Update Form/Subform

[NutoAccess]

This is the first time that I’ve worked with forms/subforms and I’m looking for some guidance.

I’ve built and entry form which allows a user to enter “lane opportunities” that they are working on, the fields they enter are as follows:
Status (from a drop down box they select Open, Converted, or Closed which has several different reason).
Distribution Center (drop down box from a DC table)
Vendor (drop down box from a Vendor table)
Vendor’s City (free form field)
Vendor’s State (free form field)
Vendor’s Zip (free form field)
Vendor’s Rate Basis (free form field)
Our Rate Basis (free form field)
Order Size (free form field)
Carrier (free form field)
Conversion Date (select from a calendar)
Notes (free form)

This form loads all of these data elements into a Master Table, and is working with a problem. Not all data elements are known at the time of entry and will require updating.

I want to make another form with will allow a user to select a line from the Master Table and update it. Here’s what I’m thinking:
Status (drop down box from Master Table)
Distribution Center (drop down box from Master Table)
Vendor (drop down box from Master Table)

The results from these 3 fields would then display in a box where the user can select the line he/she needs to edit. Once selected all the data elements from above (Status, DC, Vendor, Vendor City, ect) would display at the bottom of the screen and allow the user to make any required updates.

Is this something that is possible or have I gotten too complex for Access? If it is possible are there any suggestions as to how to do it? If this is not possible are there any suggestions as to how I could create a form that would allow the user to make updates?

Thanks

[RuralGuy]

Assuming all of the controls are bound to fields in the RecordSource of the form, they are all editable at any time. That is not satisfactory?

[NutoAccess]

I want to keep it as clean as possible for the users, I don't want them going into the master data to make any updates.

[RuralGuy]

Assuming you will be letting the users change the fields whenever you want, why complicate the process?

[RuralGuy]

I'm sorry. I don't mean to be obstinate. I'm sure what you want can be accomplished and I'd be glad to assist. It just seemed to be overly complicated for no particular reason. I've always found the simpler the process, the easier it is for the user; especially if the users are trustworthy. You can always add in tracking of field changes behind the scenes if you want to undo something or track who made a particular change.

[NutoAccess]

No worries RuralGuy.

I've been looking at it more from a user stand point. I'm used to using data fields and look ups on web interfaces and was trying to replicate something like that is Access. Personally I think it would be easier if the users used the forms, especially when the MasterTable grows to more then just a handful of records, but I could be wrong. The people entering and updating the fields in the database haven't been assigned yet so I don't know how trustworthy they would be, I'm assuming they would be fine but you never know...

I wish we had the capabilities to make this a web function however at this time we aren't able to.

[RuralGuy]

Is there some reason the user should not see all of the records?