Unbound ComboBox

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

In my table I have a Field called [Status] which could be pending, complete,
cancelled. I also have other fields in the same table [CancelledReason],
[PendingReason], and [Complete]
I have a continuous subform, and in my subform, I have a a combobox that if
one selects a status e.g., Pending... To avoid putting the [CancelledReason],
[PendingReason], and [Complete] on the subform, I thought it would be a good
idea to have unbound combobox on the Form so that when I select the type of
status e.g., Pending then the unboundcombo box turns to be the
[PendingReason] so that the user can select the reason its pending.... etc,

Is this practical, please help!
 
JOM,

Before I know how I would think about this one, it depends on a couple
of things. Let's suppose the item's Status is Pending, and you have
entered a PendingReason. Now, let's suppose life moves on, and the
Staus is changed to Cancelled or Complete, which I guess would
eventually be the case with any Pending item (am I right?) Ok, if this
happens, do you need to retain the information as to the reason it was
once pending, given that is now not pending any more? If you do, do you
want any historical tracking of this process, e.g. when it changed from
Pending to Cancelled? And anyway, what sort of information goes in the
Complete field?
 
Thanks for your time, You are actually thinking of what am thinking, if the
status changes from pending to complete or cancel, I don't need to keep track
of the past, that infomation will be deleted from the table and since the
current information is Comple or cancelled then that is what I will keep.
For complete, there should not be anything, Thanks for asking that... The
only ones that have reason are pending, and cancelled

Steve Schapel said:
JOM,

Before I know how I would think about this one, it depends on a couple
of things. Let's suppose the item's Status is Pending, and you have
entered a PendingReason. Now, let's suppose life moves on, and the
Staus is changed to Cancelled or Complete, which I guess would
eventually be the case with any Pending item (am I right?) Ok, if this
happens, do you need to retain the information as to the reason it was
once pending, given that is now not pending any more? If you do, do you
want any historical tracking of this process, e.g. when it changed from
Pending to Cancelled? And anyway, what sort of information goes in the
Complete field?

--
Steve Schapel, Microsoft Access MVP
In my table I have a Field called [Status] which could be pending, complete,
cancelled. I also have other fields in the same table [CancelledReason],
[PendingReason], and [Complete]
I have a continuous subform, and in my subform, I have a a combobox that if
one selects a status e.g., Pending... To avoid putting the [CancelledReason],
[PendingReason], and [Complete] on the subform, I thought it would be a good
idea to have unbound combobox on the Form so that when I select the type of
status e.g., Pending then the unboundcombo box turns to be the
[PendingReason] so that the user can select the reason its pending.... etc,

Is this practical, please help!
Click to expand...
Click to expand...
 
JOM,

So therefore, you only need one field in the table for reason, i.e.
StatusReason. And therefore you only need one combobox on the form, and
it will not be unbound, it will be bound to the StatusReason field. And
if you want the dropdown list of items in the combobox to be different,
depending on whether the Staus is Pending or Cancelled, you can use code
to adjust the Row Souyrce property on the combobox's Enter event. Hope
that makes sense.
 
Back
Top