Search results

First step in any good database design is to setup your tables properly. One way to learn this is to read up on Normalization. Having good table structure will make developing a database a lot simplier. As to your question, yes you can do it. What I would suggest is to have two tables...

Use a union query: SELECT [Cust_alpha], [Product_Line],[Cust_type], [Analysis_Code], [Total_value],"LastYear" as [FromYear] FROM lastyear Union select [Cust_alpha], [Product_Line], [Cust_type], [analysis_Code], [Total_value],"ThisYear" as [FromYear] from currentyear I added the FromYear so...

Add the Customer Number again and change the Total: to Count. For the Date Field ( I hope you are not using Date as a field name...it's a reserved word) change the Total to Where. That should do the trick

You can simply use the Count Total instead of sum. Just add the yes/no field, set the criteria to -1 and simply select Count in the total line.

If the departments utilize forms and such on paper, make you ask them to bring it. The paperwork is a great way to find out ALL the data that they are looking to save. Nothing like getting your tables done and a few forms only to have someone ask you "Hey, where is the spot for their best...

I understand what you are looking to do. What you want is a Dlookup. It would look something like this: Dim sSecondToField as String sSecondToField = DLookup("[EmailAddressFieldName]","tblUsers", & _ "[UniqueFieldName]"= & Chr(34) & UserUniqueField & chr(34)) & ";" Then you can set the...

The first thing you need to do is to plot out the table structures. The foundation of a good db is a good table structure. As for it being used by several different departments, not a problem. You should have a backend to store the tables. You then create a front end that each user will have...

Are you looking to put in the name based off of a record in a table, or do you want a message box to pop up with a place to manually put in the person's email? The Input box is easier to explain without knowing your table structures. Dim sInputBox as String sInputBox = Inputbox("Please...

Did a bit of googling...and are you attempting to add duplicate records as well?

When you did the debug.print, did you take the Sql string from the Immediate window and paste it into an empty Query to see if it would run?

Also, the syntax of your requery is wrong. Should be Me.Requery. From VBA Help:

I am assuming that you are using the Query Builder Grid to add the criteria. Also, what happens when you run the query through the Query Builder Grid with known values?

Have you done a debug.print strSql? Also, not sure if this is the issue, but dunno if the {} brackets are valid for a sql statement. You also have spaces in some of your field names (chk_FirstPoint Resolution). Put brackets [] around those (One reason why NOT to use spaces in field names.

A bit confused. You ask: You say you are trying to 'extract' data from an sql server, but yet you are using an INSERT sql statement. Which is it? As the error statement says, you are not providing the Values for the fields you are specifying in your INSERT statement. An Insert query...

I think I get it.... You want to use criteria for multiple buildings and want to be able to choose them with a combo box. Something like this: WHERE Building = 'Canada' OR 'North America' I can think of a couple of ways to do this. One, you could have a temp table that stores the data for...

Why not just use an update query? UPDATE tblTest1 SET fldLoop = Clean(fldLoop);

Glad it worked out for ya and happy to help out :) Oh, forgot to mention, the function only works if the deliveryDate is a week or less. If you need to calculate for a greater time frame, you are going to have to add code to test to see if the DateDiff() is greater than 7 and adjust the sql...

Sounds like you might have a normalization problem. The reason why I say this is because of this: If you have some kind of record that has multiple fields like Building1, Building2, Building3, etc then you have a normalization issue. This kind of relationship is called a One (One main record)...

Alright, check this out. I had to create a new table for the Averages. Basically, I created a table where there are 4 fields fields. Primary Key, ProductID, AvgAmount, DayOfWeek. I simply did an update query for each day to dump the data from the orgininal table into the new table. I then...

:) Good table structure + GUI query builder = Hassle Free Development