Need help with an expression in Access

[Cass]

We are using a form which has two fields: Main Topic and
Subtopic. The way we want it to work is that when a user
enters the Maintopic, a list of the possible Subtopics
comes up. Once a Main Topic and Subtopic are selected,
they should remain in the record until the users changes
it (if s/he ever does).

What IS happening is that the Main Topic works fine.
Buuut... the Subtopic, even once selected, does not stay
with the record. In fact, if on record 806 you
select "Plan" as a subtopic, and then you switch to record
801, the subtopic remains "Plan", even though that is not
the subtopic selected for that record.

We've tried a lot of options and now we're all just silly
from the whole thing.

Can anyone help?

 

[Gary Miller]

Cass,

Are you sure that the Subtopic control is actually bound to
the Subtopic field? Sounds like it may not be.

--

Gary Miller
Gary Miller Computer Services
Sisters, OR
________________________

 

[Guest]

When you say "Subtopic Control" which part are you talking
about? (So many people, here in particular, use different
phrases to mean the same thing and I just want to be able
to actually answer you correctly.)


Cass

 

[Cass]

The resolution that was previously created was a "refresh"
button. But it's not intuitive. A user wouldn't know what
it was for until someone tapped him/her on the shoulder
and said something.

Anyone...?

 

[Tim Ferguson]

The resolution that was previously created was a "refresh"
button. But it's not intuitive. A user wouldn't know what
it was for until someone tapped him/her on the shoulder
and said something.

Anyone...?

The usual way to do this sort of thing is to have a series of combo or list
boxes, and to trap their AfterUpdate events. In each case, the code would

(a) optionally rewrite the Rowsource query for the next list,
(b) Requery it, and
(c) put it to some useful default value, or clear its selection
altogether

The last list in the chain would do something like

(a) optionally rewrite the Forms RecordSource query and requery it
(b) or else use the Bookmark property to point the form to the
appropriate record

I agree that it should not be necessary to use a command button unless, for
example, you have a clumsy user interface and users are complaining that
they are having to wait while the wrong record is being fetched before they
were ready for it.

HTH


Tim F

 

[TC]

Isn't it strange how people use the newsgroups sometimes? In this case, the
OP clearly assumes that everyone she has talked to before, will
automatically see & read all of her posts, & relate them back to the
original topic. She does not see it from the respondents' viewpoint, which
is, that they respond to hundreds of posts, every day, from all over the
world. It's the same when people say, "I get an error, what is the cause?".

They< can see the error message, so they apparently assume that everyone

else can see it also!

OP, if you are reading this, I'm not trying to be rude to you. Just to point
out the reality of the situation. These newsgroups get hundreds of posts
from hundreds of people all over the world, >every day<. There is no way
that anyone can keep track of seperate posts, unless you stay within the
appropriate thread. Gary has been kind enough to pull it back in line, so
please reply to his questions, then he/we can help you.

Cheers,
TC

 

[cafe]

I agree completely. I used to reply to such posts with:

"Help, my car doesn't work, what is the problem?"

but I've given up doing that now. It was meant to make the poster think,
"Gee, he's telling me that I have not provided nearly enough information!"
But I came to the conclusion that it did not prompt them to think that, at
all.

On a related tack, I recently started drafting some notes about how to get
better help. "Use good subject lines, provide the actual error message," &
so on. Then I realized the awful truth. The people who need to read such
notes, are the very people who just won't do so! Conversely, the people who
will bother to read such notes, are probaly doing things fairly ok to begin
with. So I gave up on that idea :-(

Cheers,
TC
(off for the day)

 

[Gary Miller]

Cass,

I think that some of us (TC and myself at least) are
starting to get somewhat confused. You posted a
communication that I assume is on this problem as a fresh
thread which means that it came in as a standalone new post
and nobody reading that could tell what prior conversations
you were referring to.

What I think would be helpful at this point is to...

1) tell us what kind of control(s) you are talking about.
You refer to 'list', but that could be a listbox, combobox
or even a subform.

2) copy and paste any rowsources or code that you are using
to populate this control.

3) tell us what, if any, fields the control(s) in question
are bound to.

Your original post you stated that one of your major
problems was...

"In fact, if on record 806 you
select "Plan" as a subtopic, and then you switch to record
801, the subtopic remains "Plan""

This led to my suggestion to make sure that this control is
actually bound to a field in your table or query. If it
isn't, yes the selection can carry over to the next record
and not get stored anywhere.

If you keep your communiques on this issue in this thread
through the use of replies, it will help the many talented
folks here be able to overview the whole communication and
get a better picture on how to best offer suggestions.

Regards,

Gary

--

Gary Miller
Gary Miller Computer Services
Sisters, OR
________________________

 

[Gary Miller]

TC,

I don't know if this last week has been especially bad or
what, but I am astonished at the clairvoyence that people
assume the list experts must have about their questions.
There have been ( No, not you Cass <gr> ) some amazing
examples of questions impossible to tackle with the info
given or, more importantly, not given.

Regards...

--

Gary Miller
Gary Miller Computer Services
Sisters, OR
________________________

 

[Tim Ferguson]

I agree completely. I used to reply to such posts with:

"Help, my car doesn't work, what is the problem?"

Actually, TC, this is a sore point just now as my car's timing belt broke
this week and the nice garage man just told how much it's going to cost to
fix the damage... <boo hoo>

Tim F

 

[TC]

Actually, TC, this is a sore point just now as my car's timing belt broke
this week and the nice garage man just told how much it's going to cost to
fix the damage... <boo hoo>

NASTY garage man! NASTY garage man!

TC