Search results

Put a unique key on the fields that make a record unique. You can do this from the table design and find the key tool (different place for different versions). Pick a name for your key and apply that name to all the unique fields.

I figured there were probably reasons. The advice is still valid. A table with 30 fields seems to scream "not normalized"! Thanks for taking it in the right spirit!

Because nobody wanted to buy it, I had to move because of my work, and I couldn't keep it rented for 1/2 of my mortgage payment. In fact, I did sell it on behalf of the mortgage company on a "short sale", which means I sold it for less than my mortgage. Under those conditions, the mortgage...

And I bought my house in 1999 for $119,000 and lost it in 2009 after the price had sky-rocketed to $300,000 in 2005. Now I rent because nobody will finance me.

Not related to the answer to your question but it could impact it. Not knocking you, I'm just trying to be helpful. It appears your design does not make use of normalization. I may be wrong, but you really should never have to do what you're doing. If you look up normalization, you'll find...

Bind your table(s) to your forms and use the form wizard. Once you have it working, then you can modify it to suit your tastes.

Correct. There are few times in Access when you'll actually need to use code to do something (other than SQL).

The Microsoft Office web site has some excellent tutorials, too.

Agreed on all counts. I ran BT at 70 with a ton of 80s and it was very difficult. Just because you're running it at 80 doesn't mean you don't have to follow good instance rules. Bad DPS can still take a 70 (or even 60) raid down. Just an interesting thing on Kara & Molten Core: we 3 manned...

I think all DK builds have good tanking tools. I'm just "told" that Frost is the best. At 70, I tanked for some 75-80 players and was able to hold aggro just fine.

=(find(")",a1)-find("(",a1))-1

For the second part, you could take a look at the DCount() function. For the first part, when are you going to clear the field? Is it over the life of the system, this session, this computer, what? What if the user (or a different user) displays the same record twice within your defined...

Yell if you have specific questions along the way.

What you are suggesting is a bit complex. A good starting point would be Allen Browne's article here: http://www.allenbrowne.com/ser-24.html. That should at least tell you how big this is (pretty big). If you decide to tackle it (i.e. the above functionality isn't enough), you'll need unbound...

You haven't given us much to work with so here are a couple of thoughts: Is your combo-box bound? If it is, you will be updating the current record, not searching the table/query. Is there any code behind your combo-box? Look in the properties of the combo-box on the Events tab. If not, and...

The OP didn't tell us his requirement or even mention what his problem (if any) was. He asked if a function works or not (then going on to say he could use something else?). An odd question since it is obvious that it works or Microsoft would not have included it in the product.

Oh, gratz David! Does this mean you owe us $25?

Also, realize that "NOT IN" is notoriously slow. If you have a large data set, you might want to optimize the query. Since you didn't mention what problem you are having, there's not really much way to give you any further advice.

Your text description does not readily convey what you want. Try looking at Pat Hartman's M:M demo on this site.

[/LIST] That's an outrageously high number. It is clear that whether we are in a boom or a bust economy, 10% of people (in one case, 200,000 people) will not be applying for a factory job. Things will influence whether people would look for a job like that. Do they even know about the job...