Search results

Any time you put a 0 in the denominator, you will get an error message no matter what comes next.

This viewer thing has me baffled. I thought the snapshot viewer was contained within the SNP file. Or is it in Access and everyone I send a snapshot to has Access? Do the people viewing your report have Access installed? Not questioning you, Neil, I just thought I understood the snapshot...

No that would be too easy.

While sitting with future wife in public ... ex-girlfriend walks up after not seeing you for a few years and exclaims with visible excitement, "HOW HAVE YOU BEEN? I'VE BEEN LOOKING FOR YOU! Here's my number. Call me. Me (trying to get out of this): "Oh, gee, I don't have a pen." Future wife...

Absolutely, Fizz, thanks. I haven't had the need for that yet, but was thinking that was the purpose. Always seeking knowledge. Hmm ...

Now I have a question. I notice in both of your examples that in the junction table all fields are PK. Why? My first thought is to make all fields required. So if you book a venue, you must fill in the date. Am I on the right track or in the weeds as usual?

I think too, in some cases, you're going to need to learn about DLookup for those things you want to 'autopopulate' (good search term).

Also, check out Pat's response here. db design

Create a table that lists the choices to vote for. Create a table with choices for how strong they feel. Create a table with choices for the biggest problem, if you are going to have choices. You would only create that 3rd table if you are giving the voter a choice. If it is their opinion on...

My personal favorites.

Healey's point system Hay, you forgot to mention that we start the game with -100.:(

Have to agree with Vass's points here.

Re: Shivers? Not me Since this came up again after I joined, I'm going to make a few observations. Starting with: Freddy's wife apparently reads this forum. Chicken!:D

ptaylor, compacting at close would keep it from bloating I believe.

If this is the report that relies on a date range and you have no data in that range, the report will be blank.

Pat, doesn't this occur when you have a null value from a linked table? I have had trouble with this before , but found that the query wouldn't bring a record across where certain fields were null. I worked around this by have default values in those fields...

OK, checked it out. Get rid of the label you currently have for the report title. Insert a text box without it's label. Set this text box to: ="Customer Complaints for the Week " & [Start Date] & " thru " & [End Date] Notice you entered those values as the parameter when the report opened.

Check out the report in that last version. In the text box for the customer name and the other name fields for that matter are have their data fields set to: =[tblCustomer.FirstName] & " " & [tblCustomer.SurName] Of course, for the manager's name put in tblManager and so on. Some one correct...

Here are a couple more updates. Notice the parameter statement in the query. Everything is working fine in this one. One other thing I meant to mention. If you leave a null value in a field that is linked to a table, it will not come through to your query. I always make sure I have some...

I updated this a bit. Saw a double link I got rid of. Also, I got to thinking about the customers. If there is only going to be one customer per complaint, which i assume would be the norm, I don't think you need them as a separate table. I would incorporate their data directly into the...