Search results

After a quick glance, your ad hoc relationships in your query, built on a bunch of non-unique value/non-indexed fields, are what's stopping you. You're doing joins on fields that don't have unique indexes. Glancing at your structure, and I'm certainly no expert by a long shot, you have a bnch...

In the Design View of your query, put one of the two lines that I posted before in the applicable field/fields: Will give you every record that has an instance of "abc" starting the field off. So it would give you records with "abc" and "abca" and "abxc2342riojfosjdf34kj" occuring in that...

If you know there are going to be similar characters in each field, use wildcards after your criteria: Like "abc" & * You might try combining it with a parameter prompt: Like [Your question here] & "*"

Holy smokes, Rich, I think you've done it. Will this code function in 2000/2002 as is?

Ghudson, thanks for the tip. I've actually looked at that DB before (since it was rated so highly, and with good reason), but I never thought of modifiying the code for this sort of thing... But let me ask: Is the process really that complicated? I thought the functionality I was looking for...

Thanks for the quick reply Doc Man, but I'm really terrible with working out VB code on my own. I can usually (okay, a little less than "usually") decipher what's happening in pre-existing code, but if you've got a moment, I'm going to need more guidance with the advice you gave me. Because...

Because my users like the standard safety net of "Do you wish to save these changes?", I used some code from this post in the Before Update event of many of my forms. However, many of the users, being proactive, conscientious sorts, like to Save on their terms. So I put in a command button...

Well, the examples in the thread you found are using VB code to do most/all of the work. If you go to Design View on the forms, open the Properties Window of any ofthe command buttons, you will find [Event Procedure] listed under the "On Click" event. If you focus your cursor on the [Event...

It will only search for what you input. This might not be the end solution for you, but I'm sure it's going to be your starting point. Did you actually try using this yet? Give it a whirl, and I think it might answer your questions. The first wild card will allow for variables before your...

"Like" - This is stating the quality of the critera you will define. Other options include "<" (less than), ">" (greater than), "=" (equals), Is or Is Not (used when working with possible Null values), etc. * - This is a wildcard. It will return all values. & - Concantination, in human terms...

What you need is a parameter query. In the criteria space in the desired field in your query, put the following: Like "*" & [Search by word:] & "*" When you run the query, a message box will pop up that says "Search by word:", and then you could type in "mountain" or "goat" or even just type in...

Good guess, but no, my reeeeelly beeeeg company isn't Boeing. :D To answer some other questions: My company actually has several tiers of IT, depending on which sectors are being served. There's an enterprise level IT which serves the whole company, then there are group IT levels, and then...

Thanks for the tips, ReAn. This was one of those cases where management said "Build us a database for our team!" and I said "Okay, give me two weeks!" and then yesterday at 5, as I showed them a prototype for the look and feel, they said "Oh, about these business rules you wrote up, they look...

After poking around the forums and looking in Access help under "specifications", I see our pals in Redmond say that Access can handle 255 concurrent users. (I spit out my soda with a chuckle.) After poking around some more, I see that the consensus is that Access will begin to choke depending...

That's how I do it...as long as your countryID is what's being stored in the other table (Foreign Key), and not the actual name. You know, I've never tried that. I'll have to give it go. In my case, I've always made special pop-up forms for users if they want to change/add/edit lookup tables...

Hey Qamar, What you're using isn't a "lookup table", it's a "lookup field". Lookup Fields are generally frowned upon, as they're not very stable, they're tough to update if/when your DB structure changes, and they're not upgradeable if you have to bump up to a different database type than...

Hey Jeo, I took a quick glance at your tables, and if I'm looking at it correctly, your table structure is wrong. You should be storing dates in the joined table, i.e. tblProjectStaff. tblProject will probably rarely change (only as new projects come your way), and tblStaff will rarely change...

:D No, Sarge, it was a good dressing down. Exactly the sort of wake-up call pig-headed newbies like me need sometimes. In fact, based on tons of suggestions from you, Doc Man, KenHigg and Kevin_S, this weekend I've restructured the entire contractual DB we'd been using, and while I was at it...

The short answer = No. The long answer = You need to look up "normalization", both on these boards and on Google. Regrettably, MS Access Help doesn't even MENTION normalization. If you doubt how important it is, check this thread and pay special-super-duper attention to the comments from Pat...

Hey PaulA, I'd start by double and triple checking that the fields that the child and master are linked by are named correctly. It's very common that, when you change the name of a table, a query, or a field in a table or query, that Access doesn't follow the whole chain of what is linked to...