Search results

Just say NO to the "one big table" sceheme. It will only make life harder for you down the road. Search this forum on the words "normalization" and "design" separately. Check out O'Reilly's book on using MS Access - it covers design problems and why not to use one big table. Read up on...

Does it have to be .csv?

This is why you need to read through all those sources and look at NorthWinds. Lesson 1: Designing Tables Don't put info about more than one kind of thing in the same table. You got customers, you got orders, you got inventory, then you better have three tables. Read this and this and this...

What do you mean it didn't work? Describe your table structure and what kind of relationship you tried/desire. Why are you trying to write a subtotal to a table? In general, there's hardly ever a need to store a value that you can calculate from the info you're already storing.

Every control on the subform's design will tell you where the data comes from in its properties. Just detail what you want to accomplish, what you're currrently doing, and what results you are getting. Enough.:rolleyes:

Almost forgot... Oh, yes. Once you have your separate tables... I'd actually go with 3 tables: Customers/Accounts, Titles, and Inventory. That way you only have to enter info about a title one time and let inventory keep track of the actual number of copies, which ones are in the store vs...

RTFM / STFW Stinga: She just gave you all the tools you need to solve your OWN problems. Because we seem to have a rash of this happening right now, and because none of the culprits seem to be reading any posts except their own, I will repeat what I said to Krillin and to Tech. This isn't...

Sam-- Still no time to experiment with this, but it occurs to me to check and make sure you're not encountering difficulties relating to the differences between how Access handles 0's, Null's, and blank fields. Check Access Help on that #Error message and also read the help pertaining to the...

Check out DoCmd.Minimize. Also, examine setting the Visible property to "No". All this info is available in Access Help. --Helpful Mac

I haven't had any time to dive into bj's file, but here are some top-of-the-head thoughts until he has a chance to respond: I'm guessing that what you're seeing is NOT a text box "copying" info from a combo box, (what would the point of that be?) but that the combo box is controlling what...

I wasn't by any means suggesting that you shouldn't ask any more questions. Just that you should try to work things out on your own first, search the forum and other resources second (chances are good someone else has already asked your question and had it answered), and post your questions...

Len: THANK YOU for that. The other great thing about this forum is the fact that people DO go back and post their solutions, so that others searching later can find them. Kudos. --Grateful Mac

RTFM / STFW Tech: As you have discovered, this forum is an amazing resource for both beginners and advanced users to get help. In general, most folks here are happy to help out newbies because everyone here remembers when they were the ones banging their heads against the monitor...

Absolutely, Col! K, it's precisely BECAUSE the program is so complex and has so many facets that you need to plow in and muck with it. In fact, I have found that a lot of the best material (including some amazing solutions offered on this forum) didn't make any sense to me UNTIL I had run into...

I don't know that your references are actually valid, but I see one big problem right away with: =Iif([MaillonLocation].[Report].[HasData],"","") The reason it prints blank all the time is that you have both your true AND false values set to "", as the syntax for Iif is: =Iif(<<test>>...

Krillin: You can save yourself some of those future problems by NOT putting the CompanyName directly into Table2. The reasons for this are many, including the fact that if you ever need to correct or change the name of a company, you're going to have to go through every record on Table2 and...

Create an update query (check Access help and this thread) to perform the updating of the table. Then decide WHEN this update will be run (at program start, on a timer, at form open, whatever) and call the query at the appropriate time. Shout out if you need more details. --Terse Mac

But why? My question is WHY you want to store the same piece of data twice? --Puzzled Mac

Hmmm... Ok, in re: your selection logic, I'm still not convinced test #3 is required to find out if the company is qualified or not . Note that this is different from those tests performed to see if the particular record should be in the recordset or not. It seems that if we have already run...

Some clariciation is perhaps needed... I'm just getting back to the list and back to MS Access at all after a LONG hiatus, so forgive me if I'm posting the obvious, please. HOWEVER, I'm wondering about a couple things you've said along the way... It seems to me that the only part needed of...