accessdesigner said:
the CD case that it came in,
looks like a "bootleg" no color on it, black and white print with NO RESALE
- Microsoft Home Use Program,... this product is not for resale .... all over
it.....
It's not a bootleg copy. Your company has the right to make and distribute a
certain number of home use copies to its employees under its license
agreement with Microsoft, and it can use any media it wants for these copies,
even the plain CD-Rs the rest of us can buy at our local store. They're
legal copies as long as they're marked properly and the rules are adhered to,
like the day you leave the company you're required to remove this software
from your home computer even though you *paid* for it. (You actually only
paid for the distribution and administration costs to your company for home
use software, not for the applications on that CD.)
what about my program statement that still does not work? :-(
As pointed out by others, you're using incorrect syntax. The reason code
works in one place and not in another is due to either:
1) You're using it in a different context (different unbound/bound form,
different event, etc.), or
2) You're the victim of one or more bugs, where the code you see in the code
window isn't actually the code being executed at runtime.
The second reason is very hard to find and will cost you days or weeks
chasing red herrings if you develop Access applications for a living and you
don't take steps to avoid these bugs:
1) Always turn off Track Name Autocorrect.
2) Never accept the default name assigned to controls on forms and reports
where you will use these names in code, properties or macros.
3) Never use a name that requires brackets to fix it. ("Name," a reserved
word, is one of these.)
4) Before you run the code again, always save and compile the code after you
make code changes.
It's really, really hard to help you because we have to guess which mistakes
you made when you built your form. I can't duplicate both your error
messages with the form I built with the mistakes I *think* you made, which
means I'm guessing wrong. I *think* you're using a bound form with an
unbound combo box. I *think* your combo box is named NameList and its
rowsource is your query named qryNames, which uses this SQL statement:
SELECT Names.Name FROM [Names] ORDER BY [Name];
But that can't be right because I get "Variable not defined" when I use this
line:
If Me.NameList = NameThings.NameLOOK
... which means ... oh! I know what *that* means. Scroll up to the top of
every module in your application and add this line of code if it's not
already there:
Option Explicit
Save and compile. Now go to Tools | Options | Editor and make sure "Require
Variable Declaration" is checked so this never happens again. Now when you
run that line of code with the bad syntax you'll get the correct error
message.
The Query: NameThings .....is only connected to my Report
... which is on a plane headed for Moscow. Or did I guess wrong again and
NameThings is the query that your current *form* is bound to? Or some other
form is bound to? If it's bound to your current form, does this query
contain a column named NameLOOK which contains only one record that might
match the Name column in the Names table, or does this query use the Names
table as its source?
And I'm still confused what you want to do after looking at your code and
reading this from your other post: "Im trying to get a combobox selection
from a form to match what is in my query named NameThings, under the NameLOOK
field." I *think* you want to concatenate the selected item in the combo box
to strwhere *if* there's a matching item in the qryNames query. But why not
just allow the user to select from the names in the NameThings query instead
of qryNames?
I *think* your ultimate goal is to build a search form which leads me to
believe you'd have a better chance of success if one of the others helped you
with it. I don't build search forms, other than the ones that use the built
in "filter by form" and "filter by selection" toolbar buttons.
