Search results

You have to have a valid query for your openrecordset command. The following has two issues: 1. the comma before the FROM clause 2. no table or query is specified in the FROM clause (I assume it should be Archive) "SELECT Archive.num_article, Archive.Division, FROM ? BTW, you can filter the...

You can do the following in the SQL view of a new query SELECT [Data-Billing].[Employee Number], [Employee Cost centre], Count([Data-Billing].[Employee Number]) as NumberofCCs FROM [Data-Billing] GROUP BY [Data-Billing].[Employee Number], [Employee Cost centre] If you want to do this using the...

Each of your subquestions should be records in tblQuestions and you should define the response type for the subquestions just as you did for the main questions. (Normalization rules dictate that the same types of items be in 1 table). Now to relate a subquestion to its main question, you would...

For troubleshooting purposes, you could put the SQL text in a variable that way you can copy the constructed text to the VBA immediate window using the debug.print statement. From there you can inspect the SQL text for errors. You can also copy that text to a new query and test the query to...

You're welcome.

What is the data type of the tilausNro and Rivi fields? If they are numbers, the you must remove the single quotes around the two form values. "WHERE TilausNro ='" & CLng(Me.cboTilausNro) & "' " & _ "AND Rivi = '" & CLng(Me.NykyRivi) & "'" The single quotes are only needed for text values...

You might try explicitly defining the two date combo boxes with a parameter clause in your query: PARAMETERS forms!form1!cboStartDate DateTime, forms!form1!cboEndDate DateTime; SELECT BILL_IMPORTS.ownerb, BILL_IMPORTS.swhsb, BILL_IMPORTS.Ship_Date, forms!form1!cboStartDate AS WeekBegin...

The values from the form are variables and thus cannot be included in the string. They have to be concatenated to the string. Also, you should not have an = sign after the currentDB.execute CurrentDb.Execute "INSERT INTO tblTilaukset (ListaNimi, Materiaali, Väri, Määrä, MääräYks, Pituus...

Since a part requires multiple tools, that describes a one-to-many relationship. Should we assume that a tool can be used on multiple parts? If so, that is another one-to-many relationship. When you have 2 one-to-many relationships between the same two entities (parts & tools in this case)...

It sounds like you want to append the events when a case is created so the user only needs to enter the applicable date for each. Is that correct?

The date for each event would be entered via a text box not a combo box as I indicated in the tblPSUEvents. The event information would be entered via a combo box tblPSUEvents -pkPSUEventID primary key, autonumber -fkPSUID foreign key to tblPSU -dtePSUEvent (date field) -fkEventID foreign key...

Theoretically, yes you can use a textbox. But let's say your boss wants you to evaluate some performance metrics. For example, perhaps the number of days from when a case is initiated to when it is submitted to the director is important. Let's say you allow you users to enter the event via a...

If I understand what you are after, you may want to look at the Partition() function. The function can be used in control sources (forms/reports) but it is probably best used in a query.

OK, since the services do not vary by location that simplifies things somewhat. So let's start with the contracts. We'll need a basic table for the contract info tblContracts -pkContractID primary key, autonumber -txtContractNo Now, since multiple locations of a company are involved in a...

If you generalize things a bit, it may help you with the table structure. Instead of having separate tables for account managers, sales managers and contacts, why not have 1 table for all people? Similarly, instead of having separate tables for clients and vendors, why not have 1 table for...

You will need to include both the main table and the site manager table in the query. Then include the name field(s) in the query. Having combo boxes at the table level can cause some issues (just like you describe and others. Please take a look at this site that describes the other problems...

Give it a shot & then post what you have & we'll take a look at it. The structure will be similar to the tblPSUEvents we discussed earlier No, separate tables for similar information generally goes against normalization rules. Could you consider the time line as just a series of events (and...

OK, I took a quick look. You have repeating information in several fields of your PSU. To make data entry easier, it would be best to put the possible choices in a table and link that table to your PSU table. For example, you can have a table of complaint origins/originators with 3 records...

I prefer to work through the forum rather than e-mail. All I really care to see at this point is some representative/sample data in the tables. To reduce the size of your database, run the compact & repair utility within Access and then zip & post the file. If the file is still too big...

OK, regarding the following fields, can you explain what the data type is for each field and a brief explanation of what type of data will be entered? I am trying to understand if you have other relationships in your data.