Search results

I see the error, it is mine. Change FROM tblCASE INNER JOIN tblOrder ON [tblCase].[CaseManagerID] = [tblOrder][CaseManagerID] to FROM tblCASE INNER JOIN tblOrder ON [tblCase].[CaseManagerID] = [tblOrder].[CaseManagerID] NOTE: I left out a table.field separation point out of the first...

Create a SELECT query. You don't need an expression builder. Since you have two tables involved, I *assume* you have a key field defined, probably the Primary Key for the Case Manger, with its corresponding Foreign Key in the table containing the client and order date. Here is the query with...

Try Left(field_name, 3)

An aggregate query would be the best answer. Since you are finding the record of the FIRST order, which means the EARLIEST order date, you would group the aggregate on the Case Manager, as follows (tblCASE is name of table): SELECT [Case Manager], [Client], Min([Order Date]) AS FirstOrderDate...

To post the list of months is quite simple. You can just set the combobox RowSourceType to "Value List", and then RowSource to "Jan";"Feb";"Mar";"Apr";"May";"Jun";"Jul";"Aug";"Sep";"Oct";'Nov";"Dec" But to use the combobox to use the values to filter, say, date values, would be a little more...

One of three ways: SQL Method: Instead of using the "all" (*) indicator, you can select every field individually. However, replace the date field you want to format to an expression. Say your field is called "MyDate", then the expression would be: SELECT Format([MyDate], "m/dd/yyyy") AS...

You can have 255 fields in an Access table. However, a table with that many fields usually indicates an improper database design in the first place. What type of data will you be processing? I myself have never had a database with more than 25 fields. Check to see if you have repeating...

Dan, If your MDB file, zipped, is under 100K then post it. The query I emulated was not VBA, but a query that accessed a form and table to your name specifications (with the exception of the relative "Me" assignor)

Sorry. I'm sorry, I was using the Design View format, not the SQL statement format. When you open your query in Design View, you will know what I mean.

I think I get his point. First, let's assume a query that returns records sorted on a unique field to prevent possible duplicates. He wants to return a specific number of records starting from a record number that is in a specific location of a sorted query. For instance, "TOP 10" would...

Since your format is a rather simplified Text string format using date constants, try: For current Date: Period: cstr(Year(Date())) & Format(Month(Date()), "00") For explicit date (use "#" as the delimiter): Period: cstr(Year(#April 17, 2005#) & Format(Month(#April 17, 2005#), "00") For date...

I emulated the db and query. I used: IIf([Me].[Custom1Checkbox]=-1,([tblPart].[Description]) Like "*" & [Forms]![frmParts]![TxtFilter] & "*",([tblPart].[Description]) Like [Forms]![frmParts]![TxtFilter] & "*") It worked, but I had to use an explicit form reference. Have you tried replacing...

Office 2003.

"Select" is one of those words you should never use as a field. Generally, any word that is identical to an action or function in Access should not be used, such as Select, From, Now, etc. Change it to "Select_1" or something similar and see what happens.

The error is occuring because yoru field "Due Date" is a TEXT field, and "Date Approved" is a DATE/TIME field. If both fields were text, or both fields were date/time datatypes, then the function would work. However, when you are trying to perform a function on two different datatypes, you get...

Do not use "Sum" as a field name. It is a dedicated name or function in Access. For the same reason, don't use "Date", "Now", or other names that are intrinsic to VBA and Access. Ken's example is correct. Just change the name of the field.

Access can be quirky. Fields which don't contain data may not necessarily be null, although date fields (which are technically Double numbers) should register null. Therefore, if checking for null values, you may have to further query to for zero-length string values (which are NOT null...

I had no problem with your query. I recreated all your fields, and table. I even changed the datatypes from date to text, still get no errors. There is one more issue that may have an effect: Reference assignment. Do the following sequence: In the menu for the database, select Tools, then...

Post the SQL query. Sam's answer is valid, so your fields are not matching.

You have to change the date fields Date1 and Date2 to the fields that correspond to your table or recordset you are querying.