Search results

What happens if 2 people push the button at or near the same time?

It takes somebody like Banana, or maybe Leigh, to even follow along. I just wrote the words 'cause I though they sounded cool.

I wish. It's been 10 years because I'm too lazy to finish it.

Remember, I said "may" (I always leave myself an out). I've been working on an example for 10 years that you and I have discussed before. When it gets down to it, I'll discuss it with you then and try to remember to update this thread.

Actually, this may be useful if your design utilizes polymorphism with a multiple table implementation.

I wish. But Excel and Access do two different kinds of things.

I hope you're ready to learn: http://www.databaseanswers.org/tutorial4_data_modelling/index.htm I don't imagine most members here would be willing to give you their work for your school work.

I'm not sure that people would bother looking before they ask their cookie cutter questions anyway. You know, people would do well to just go through the Microsoft Office tutorials before they even begin (I did). That would eliminate 50% of the stuff we see on here daily. But that is a free...

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!

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...