Search results

Hey Jeo, You've got both The Doc and Pat Hartman helping you - you're in good hands. But since you sound like you're still struggling with relationships/IDs in practice, let me tell you you're REAL close. At the risk of repeating a lesson that's no doubt been illustrated here countless...

Compact & repair works wonders, but keep in mind your database will be unuseable if one person has Forms open in Design View, and then someone else tries to open the same DB. Access will not allow you to change the layout/structure of Forms when someone else is using the database. Also, if the...

Funny you should ask that - it's on my project list to normalize it this week, starting this morning (as soon as I'm done trolling the forum anyway)! :D

You should be able to save a report as a ".rtf" file (Rich Text Format, easily readable by Word) by click on the button "Officelinks" in your toolbar when you're viewing the report. The formatting can sometimes gets a little hairy, so be warned. These office links can be handy in other ways...

Doc Man, thanks for this explanation! I always had a notion of recordsets that I couldn't ever quite put into words, but this was terrific. Thanks!

Put a "Count" field (non visible, of course!) in the Detail section. In the Report footer, put another field that Sums the Count field. Search for "Count" on these forums and in Access help for more info.

I've found it necessary to store store stock quantities before to aid in internal audits - I often have to deal with forecasting and procurement/buying departments, and they need to be able to track trends in quantities, warehouse stock, shipping quantities, and suppliers, usually over multiple...

There are a number of ways you could set this up - for ease of viewing, I usually use "Count" fields in the query, and "Sum" fields in text boxes on forms/subforms. If you just need to look at this quickly, you might have some luck using "Find Duplicates" queries, which Access can set-up for...

For a year, try putting this in your Criteria field: Year([YourField])=2004 Or whatever the year is. Look in Access help under "Year" or "Examples of Expressions" for more info.

In a desperate effort to get this thread back on track (remember when it was a philosophical discussion of normalization? Way back when? Somewhere around post 50 and before?), I want to thank some people, and then I'm out of this thread, because this discussion has made for some strange...

Right. No. I fear I've been a bit misleading. Each company/vendor can have many contracts, but each PROJECT THEY WORK ON has a complete contract. Again, the example in my database lays it out nicely. You'll see I put in two companies and 40 some-odd projects/contracts, with 20-some-odd...

True. You'd be surprised how fast we burn through those temps. Which is why I need to keep it as simple as a spreadsheet. I'm not trying to argue that my table should be denormalized - I WANT to do this right. In my example, I even put an extra joined table in, doing EXACTLY what you said, Kev...

It's all those things. But, honestly, my department, is only concerned with dates. The legal department can handle all the other crap. All we care about is when we get a copy of each component in our files. I'm not going to do the legal department's tracking for them! :eek: Hahaha, I didn't...

We track when they come in. Otherwise you're spot on. If you look at the sample DB I posted earlier in this thread, you'll see that we track dates of when all these components come in. So, different parts might arrive on different days. Is it possible, since we're tracking dates per component...

Is that back when databases were all in black and white? Great points Pat, and lots of good things to think about. This thread has generated lots of food for thought that's going to take me a long time to take in! Here's another example, with two sets of tables. The is "tblGCContracInfo"...

I figured the data would be added the moment a company says "Okay, we'd like to work with you" - then we add their name to our database, and wait patiently while they send in thier contact components. I have 4 or 5 users who enter the data, and they like to see a nice screen like the one I've...

Don't worry, I don't. :D I was just trying to cut to the chase/confirm that I got the gist of what Pat was outlining. 10-4 good buddy. Thanks!

Just fixing the link. :D W/r/t the querydef - all your suggestions are great, and are exactly the sorts of pitfalls that I want to avoid in this. I want to keep all the DBAs and IT folks as chipper as possible, and this sort of heads up will help. (One quick question - you're mostly telling...

Makes sense, Ken, but our lawyers have already decided: "If companies want to work with us, they will fill out this contract - NO CHANGES." If other companies don't like it, we say "Well, it's been a pleasure" and we go our merry way. So - there are never any changes. These are the parameters...

I have a case where, despite stern talking-tos from Pat Hartman and others, I've been using a denormalized table, because it's made it easier to set-up in forms and has kept the records to a minimum. My example: My company has other companies with whom we work (tblCompanies, with 90+ records)...