Search results

need more info here which table is your customers. What does tblMain represent. What do the feidls in tblAction represent? Anything else you can explain about work flow

I do NOT recommend composite keys. They tend to cause more problems then they are worth, including the one you are encountering. I recommend using an autonumber as your primary key for all tables. If you want to enforce uniqueness on a combination of fields you can do that using a multi-field...

I have to disagree with Statsman's advice here. There are three methods of DISPLAYING data from another table on a form. Those three are subforms, the Column property and DLookups. In your case, I would use a subform. The only time I would not use a subform is when the number of vlaues to be...

First, in the expression you posted, the first part of the expression returns their birthday in the current year. The second part returns their birthday. The Date Serial is totally superfuous in the second part. So the expression returns the number of DAYS old they were (or will be) on their...

Don't use a paremeter prompt. You are running this from a form. Input the parameter as a combo or textbox on the form and reference it in the query.

Wicksa, Actually what you said confirms What SJ told you to do. The expression you use for calculating age is not accurate. Your expression shows their age on the day of calculation. You really want it to be on the day of their next birthday. And you want it accurate.

That looks OK. TRY building the query in Query Design mode and see what the SQL looks like. Open a New Query in Design mode and add QRYLetterByPostcode. Select the LeadID column as the first column. In the 2nd column put the expression: LtrDate: Now() In the 3rd column put the expression...

You need to check the SQL you are generating. There is probably something wrong in the syntax.

No, because the employee name isn't repeated, only the employeeID as a FK. Especially since each type is a different rate, does it make more sense to do it the way I'm suggesting.

You can't format a Checkbox to display Yes or No. Yes or No are text strings. A Checkbox is displayed as either checked (Yes) or unchecked (No). If you want to display the Text, then use a Textbox with a IIF: =IIF([field],"Yes","No")

Having field named RT, OT, DT constitutes a repeating group which violates normalization rules. You can do your reports with grouping to eliminate repeating employee names.

I would have used a Where clause

Use a DLookup

This would be easier using SQL strSQL = "INSERT INTO TBLLetterHistory (LeadID, LtrDate, ReportName) " strSQL = strSQL & "SELECT LeadID, Now() AS LtrDate, 'RPTLetterByPostcode' AS ReportName FROM QRYLetterByPostcode;" CurrentDB.Execute strSQL Note: I change the name for your date field. Date is...

This is a many to many relation. So you need a join table to join artist to CD. tjxArtistCD ArtistCDID (PK Autonumber) ArtistID CDID

I'm not sure I would download something from someone using the name Genisyde (genocide??). What you want is to have a single table for any girl who has every been a member. Add an Active field to the table. Set the field to default to Yes for new entrants. Change it to No when a girl goes...

Dim stDocName As String stDocName = "Qry-Makes Table" If DCount(" * ", "Qry-Test for Zero") = 0 Then MsgBox " There is no data for this time frame to chart. Please re-enter your Date range" Exit Sub Else DoCmd.OpenQuery stDocName, acNormal ', acEdit End If

Ok, I was going by earlier things you said. The DSum sums a column. It coulde be an expression (i.e. DSUM([Price]*[Qty]...) But it would be easier if you did your calcs (and some filtering) in a query, and then run the DSUM off the query.

The problem is your structure. You have what is called a repeating group in table 2. that violates normalization rules. The strucutre for table 2 should be: RateID (PK Autonumber) ClientID (FK) RateType (SC, LX, SX) RateAmount From there is a simply matter to join on ClinetID and RateType to...

A questionnaire/survey/test database requires some special structure. If you do a search on one of those keywords you should find some examples. The basic structure is like this: tblQuestions QuestionID (PK Autonumber) Question tblRespondents RespondentID (PK Autonumber) Respondent...