Combining Fields

  • Thread starter Thread starter aubrey
  • Start date Start date
A

aubrey

Hi,

I have three fields in my Query: Issues I, Issues II and Issues III. The
user will select and option from either Issues I or Issue II, never both. I
then want to take the information selected from either Issue I or Issue II
and populated the third field Issue III.

Any help on this would be great.

Thanks,
 
Hi,

I have three fields in my Query: Issues I, Issues II and Issues III. The
user will select and option from either Issues I or Issue II, never both. I
then want to take the information selected from either Issue I or Issue II
and populated the third field Issue III.

Any help on this would be great.

Thanks,
Click to expand...

Sounds to me like your table design IS WRONG. Storing the same data in two or
three different fields is incorrectly normalized. What's the nature of the
data?
 
i think he is looking at doing that in order to have one field for a
query. that would be my guess as john said that is not right you
shoudl haev an issue table and just one issue field since you cannot
have both issue one and issue two filled at the same time.

regardless something like

select issueI,issueII, iif(isnull(issueI),issueII,issueI) as issueIII
from thequery;

will do that

if you dont want sql then use

issueIII: iif(isnull(issueI),issueII,issueI)

as a field int he query designer

hope this helps

Regards
Kelvan
 
Hey John,

Thanks for the reply. I have the data broken up in to two fields because the
list of total issues is very long; some of the issues are used frequently
others are not. i use the two fields so that the front end user doesn't have
to scroll through so many issues to find the one that they're looking for. i
then need to create a report where by issues from both fields are listed, on
the same report; which is why i'm trying to combine the issues from the first
two issues fields. If there is another easier way to do this, please let me
know.

Again thanks for your help.

Aubrey,
 
Onthe form where they are updating the fields:

Issue1 afterupdate event.
if isnull(me.issue1) = false then
me.issue2 = null
me.seachissue = me.issue1
endif


Issue2 afterupdate event
if isnull(me.issue2)=false then
me.issue1 = null
me.searchissue = me.issue2
endif

Ron
 
Thanks for the reply. I have the data broken up in to two fields because the
list of total issues is very long; some of the issues are used frequently
others are not. i use the two fields so that the front end user doesn't have
to scroll through so many issues to find the one that they're looking for.
Click to expand...

Um?

They shouldn't need to scroll AT ALL. If you give them a combo box, with its
autoexpand property set to true (as it is by default), they can tab to the
combo, type the first few letters of the issue, and select it. This will fail
if "very long" means over 65536 rows but that's a whole nother can of worms.
 
Back
Top