Search results

Couple of questions..how do you derive the Average for each day? Do you run some kind of query each day to calculate the total? I ask because for what i'm thinking, the table setup needs to be changed a bit. Queries can be built to find the averages, and should be used in this scenario.

Well, using a bunch of queries, I have recreated the look that you want. I've attached a db to illustrate. The data is still in the Table2 format, but there is a query (Query1) that emulates the look of Table1.

Add the products table to the query and link it to the IncidentDetail table. Add the Obsolete field from the products table and set the criteria to No. That should do the trick.

glad it worked out for ya!

with different averages, yes. It should work with different delivery dates as well. I gotta head out....but if nobody jumps in, I'll see what I can come up with tomorrow. Could you post a sample db with a few rows of data from the tables in question? Would help to see how the data is setup...

I have to take off now....I'll take a look tomorrow if nobody beats me to it :)

What is the sql statement that you tried? I put the brackets in there to signify the different field names that you want to add all together. You need brackets if your field name(s) contain spaces (It's a habit to include them when helping ppl out).

it makes sense..but you are right, using dlookups is more than likely what is slowing it down. Dlookups should be used sparingly...what you are trying to accomplish can be done with a bit of code and a well defined query. This is what is floating around in my head. First, Calculate the number...

You want an update query. Something like this: UPDATE af1_temp SET card_Number = [Field1] & [Field2] & [Field3] WHERE nz(card_Number,0) = 0 What this will do is to update card_number with the concanted value of the three fields when card_number = 0. The Nz() function replaces a null value...

I'm the same way...I learn much better by actually seeing something rather than having it explained to me. All you need to do is to record the StartTime and StopTime of the Project and Device. By using Now(), it will record the date and time. So, when a project is created, you can have the db...

That's correct, you cant update a table using the * you have to specify each field so that access knows what data to put into what field

Oh, I agree, (I store calculations in a few tables as well for performance hits). Its just generally easier to tell ppl to not store them as a general rule :) Well, off the top of my it shouldn't be that hard. Let me see if I got this straight: You have a table that has the average cases...

Actually, having JobDetails (Each separate repaired item) isn't that difficult. What you would do is have an additional table: tblJobDetails JobDetailID (Primary Key) JobID (Foreign Key) Quantity RepairItemName HoursWorkedOn RepairBillabeRate etc, etc, etc

The sql will be something like this: INSERT INTO tblCustomers (CustomerID, CustomerName, {Other fields}) SELECT tblTemp.CustomerID, tblTemp.CustomerName {Other fields} FROM tblTemp RIGHT JOIN ON tblTemp.CustomerID=tblCustomers.CustomerID WHERE tblTemp.CustomerID IS NULL I'm not that good...

Would it be possible for you to post the db? You can take out any sensitive data (or better yet, add some dummy data). Include some of the data you want imported. I know it's easier for me to come up with a solution if I can see it in front of me. Also, if possible, upload the db as a MDB file...

You should put the code on the On_Current of the main form, not the open event for the subform. Also, not sure which fires first, On Open or On Load. If the value of the text box isn't filled because the record isn't loaded, then the If condition wont be met. Also, if you change records, then...

Calculations shouldn't be stored. If you need to calculate something, it should be done in a query. What exactly are you trying to calculate?

yes, it would be something like this: if forms!MainFormName.Form.activity = "Visit" then forms!MainFormName.Form.cmdShowVisitForm.visible = true end if

You have to properly reference the control you are trying to make visible/not visible. Here is a webpage that show you the proper syntax for that: http://www.mvps.org/access/forms/frm0031.htm

I wouldn't. You would have to continueously update it if you did that. As long as there is a primary key so that you can identify each employee you should be good. If you only need certain data from those linked table(s), you can always just create a query to get that data. You dont really...