Search results

What I usually do is to create a Query and do all of my calculations there, creating new fields as necessary. Then use the query as the datasource for all subsequent forms and reports. The calculated fields can then be used just like any other field.

Access is almost completely indifferent as to whether you are using tables, queries, or a mix of the two as datasources for a query. When you are creating a query using the wizard, any existing queries are listed, along with the tables, at the bottom of the list. If you are using the query...

I used to get this error when I was using Access 97, but not since we upgraded to 2002. What I did to workaround was to use a series of 'simpler' queries, using the previous query as source. I never figured out how many fields was 'too many', but whenever I hit the error, I just stopped...

If you are using Access 2000 or later, look up "conditional formatting"

BTW, as a matter of respecting normalization rules, why do you have more than one table with the identical table structures?

1) Do you have any unique indices other than the primary key? 2) You could create a query from your source table, containing all fields except the primary key, and then append THAT into the target table. You are going to get new numbers for the PK for these records, so they better not be used...

bozrdang: I believe you need a 'many-to-many (M:M) relationship between Molds and Parts (which involves the creation of a third 'linking' table. Check out 'many-to-many' in this forum's search to find a number of threads to show how to do this. Reply here if you are still stuck.

Try the 'Find unmatched records' query wizard, using your original table and your query that only returns 1500 records.

You can eliminate the 'iif' check in Jeff B's post as follows: INT((n-0.0001)/5)*5+5 Subtacting a very small number from 45 equals 44.9999, which becomes 8 after the /5 and INT, and results in a 45 again aster the *5+5

I agree with The_Doc_Man's comments, but feel compelled to add the following: If and when your database 'outgrows' the limitations of Access, you can 'port' your 'back-end' data to MS SQL Server. Once this is accomplished you can minimize the impact of The_Doc_Mans' Cons, numbers 1 through 4...

I associate the following code with a double-click event on my 'lookup' form. This code opens up a completely separate form and filters the contents to display only the current record from the form that is open. Obviously, you should substitute YOUR object names: : Private Sub...

First, design your report as if you want to print the entire contents of the client/orders tables. Your header should contain all of the client info, and the detail section should have the order data. PREVIEW this a few times until you are satisfiled with the layout. Now, on your MAIN form...

look at http://www.access-programmers.co.uk/ubb/Forum5/HTML/001971.html This works for 4 rows light, 4 dark. I found this much less obtrusive than white/yellow/white/yellow This same techique works well for forms too, but you have to fiddle a bit.

*** Normalization Alert! **** Why have 3 different tables? You should add a 'UtilityType' Field and store all data in one table. Then your queries and everything else gets much simpler. Look up 'normalization' in this forum's search feature or Access help for more information on how and why...

In your last post, you basically said "All that function did was give me a unique value per financial year. How do I use this?" Define a field in a query like FinYear: Year(DateAdd("m",(+/-)6,[RealDateField])) and ensure this query includes your table primary key (PK) to match the new field...

This a strange structure! Am I correct to state that a complete 'concept' is separated into two records in the same table? Will the quarter records ALWAYS be the next record after the council record (i.e. id always one greater?) If so, create a query that selects all of the records with an...

There may be a better way to get this but... The MSAccess long color value is equal to R + Y*256 + B*256^2 So you should be able to 'extract' the respective values using mod and int.

Have a look at the "find unmatched query wizard"

In a query, put ">Date()-7" (without quotes) under the arropriate date field as the criteria (or perhaps ">= Date()-7", depending on how you define "the past 7 days")

You can do this with a few queries. The first one is a summary query that groups by CategoryID and totals with Max for the ScoreID. The result of this is a list of the Maximum score for each category. The second query would include as source your original table and the above table, with...