Search results

Sure is. Create a query with the following Fields: Code (I would change the name...CODE is a reserved word) Title Quantity Amount Now, up top you will see the greek symbol Sigma (Looks like an uppercase E). Click on that, you will now see a new line for each field that says Sum. Click the...

Generally it's better to use queries, they are much more flexible as record sources than tables. With the use of Primary/Foreign Keys (Like you have now) is one big reason for doing so. You also can apply filters (via criteria) when using queries.

I experience the same problem...no idea why. I just got use to doing the following: 1. Resize the window a bit. 2. Resize the table window a bit. After that, it works just fine. I also get that problem on occasion with the Database windows. I just simply select something besides what is...

In the query that is the source for the report, add the table that has the information about the catagories (I will assume it's tblCatagories). Add that table to the query, and link the two CategoryID fields together. You can then add the CatagoryDesc from the Catagory table to the fields. Save...

What you want to do is to store the Primary Key field from the AccountsReceivable table in which the client is making a payment with the record that will store the payment information in the Payment table. So it will look something like this: tblAccountReceivable AccountID - Primary Key...

End of the day and it's slow :) Working on converting our database to Sql Server...and from time to time I need a break from staring at converting the front end :)

Lets backtrack a bit. I have a strong suspicion that your database isn't Normalized. I say this because: Two things immediately come to mind. First, you should never let the end user have direct access to the tables. Forms should be used to input data. Second, it sounds like you are treating a...

Off the top of my head, you will need 2 tables. One to list the Items that you build, and one to store the parts for each Item. tblItemsManufactured ItemID (AutoNumber, Primary Key) ItemDesc Other Item Information tblItemParts ItemPartID (AutoNumber, PK) ItemID (Foreign Key) PartID (Foreign...

You can use the InStr() function to find the placement of the space. Then use that to extract the digits to the left of that. YourNumber = left(YourFieldName,Len([FieldName])-InStr(" ",[FieldName]))

You can add criteria to the dcount() function. Put this in for the control source: =nz(DCount("*","devices","[ProjectID]=" & [Forms]![devices]![combo22]),0) Also, you will want to get rid of the Table Level Lookup in your Device table. Here is a link as to why you shouldn't use them at table...

A simple Dcount will do the trick for you. I am assuming you are looking for a total number of devices that are found in the table Devices. Put a text box on the form. Set the control source to: =nz(DCount("*","devices"),0) that will count up the number of records in the table Devices. You...

First off, please remember that the people here offer their help for free. Being impaitent will get more frowns and scowels that help. It's only been an hour since you posted. Give it some time. Now, as to your problem, try this: If Me.CheckPed = -1 Then DoCmd.OpenReport "rptPer_Refine"...

It's declared vididmax as a variable and used dmax to find the ID number so it's a variable. What pbaldy is saying is that since the criteria of your dlookup is based on the Video_ID on your table, then it's looking to plug in a number. By putting the extra quotes around the variable, you are...

You are on the right track. the [expr] should be equal to the ID number of the Client that you are billing. (You are storing their unique ID number with each record, right?) So it would be: DCount("*","AsbestosSample", "[ClientID]=" & Me.IdNumber) Make sure you substitute ClientID and...

DLookup only returns one value. So if you are looking to get a second value, you will need to do a second DLookup. I would do a dlookup of the Primary key of both dlookups and if they match, then you can return false. If DLookup("[ArtistID]", "[TblArtist]", _ "[artist_name]=""" & artist &...

You can do it two ways. 1. Put a combo box on the main form and any other txt boxes you might need (Quantity, etc). Have a command button that fills in the necessary fields on the subform. For example: [Forms]![frmOrders].[LineItemSub]!SKU_ID = Me!CBO_PICK_LIST.Column(1)...

What you are describing is a One to Many Relationship, and there should be at least 2 tables. One to hold the Company Information and one to hold the Contact information. You should store the CompanyID with each contact record so that you dont have to duplicate the data.

First question is...if the company already exists, why are you creating a duplicate record? If you need to record the company data with another record, you should be storing the Primary Key for that company with the record. This is called a One to Many Relationship.

Curious as to why you would use the same combo box 5-10 times per form. Other option is to put in a small list box, set the row source equal to the products table and include all the fields you want to display. Then, in the criteria for the list box, have the productID = me.comboboxname. Then...

Not really an odd issue...the combo box will only display the first column when a product is selected (as far as I know). The other columns are still available, just not visible. What you can do is to have a couple of unbound text boxes, and with a bit of code you can display the other data. All...