Reffer\Enable field in specific record on continuous form

[Rich]

If the combobox's rowsource is always same for any given row, there's no problem at all. But when it depends on another piece of data in the same row, such as a cascading combobox for example, which filter the list in the rowsource, it can cause all other records that has value that aren't in the current filtered list to go blank.

Did that make sense?

Most of my combo's on my continuous forms are cascading, I don't have any problems with them, can you give say a specific example to get ones teeth into?

 

[dkinley]

An example (not cascading though) would be this post here ...

http://www.access-programmers.co.uk/forums/showthread.php?t=154601


Another example (although not in the scheme of cascading but similar) is in a current app I am working on which is basically the same as above ...

A Case is assigned to a Person. A Case is tracked through a Case Number; however, a Case Number is not assigned (user generated) until the third step in the process. The dilemma is how do the users track the Case without a Case Number?

My first thought was simple, if no case number then case number = "not yet assigned" and they track by Person until it is assigned. That doesn't fly because there cannot be any duplicates.

So now Case Number defaults to pkCaseID. So if CaseNumber = pkCaseID hide the case number control and show a dummy control that says "not yet assigned". If CaseNumber <> pkCaseID hide the dummy and show the case number control.

For all the queries that produce on-screen lookups, I have instituted IIF's for the user presentation.

-dK

 

[Rich]

You could just set a dummy value that will never be used for anything else, say 0 and use that

 

[dkinley]

My constraint is no duplicates, tho. There can be 100's of People that have not been assigned a Case Number at that time.

-dK