Recent content by russiver

Thanks for all the replies. Although a little slow, using DSum() for the sum gives me the check list I was looking for.

Thanks. Will give that a try.

I have an accounts database that stores bank transactions in one table with a 'one to many' (transID to FKtransID) relationship to a second items table that stores the items of that transaction. The transactions table includes a yes/no field for checking off when a bank statement is received...

Thanks, that's fixed it.

Galaxiom, Checked out your code and it produces the following error: Any ideas what is causing this?

Thanks. I should have spotted that. One final question. Why do you need the table alias - FROM myTable as T WHERE Is it because the subquery uses the same table as the main query?

Many thanks for all the replies. Have tested all suggestions. Findings as follows... CJ_London, could not get your sql to work. Tried several minor alterations, but the following error kept presenting. Any ideas? Plog, read_date is unique and your code works fine. JHB, crosstab works very...

Hi all, Simple example of what I'm trying to achieve... Table with two fields: read_date---read_value -------------------------- 01/01/13-----10 01/02/13-----20 01/01/14-----30 01/02/14-----40 Would like to create a query or queries that summarises the data as follows: read_date--2014--2013...

Many thanks for the reply. Slightly confused :confused: Are you suggesting using a calculated field for each data range? So This works and produces a single row of data.

Not sure if the following is possible, but below is a simplified example of what I'm trying to achieve with a parameter query. The source table for the query contains two fields: Reading_Date (short date) and Use_value (integer) The parameter query sums Use_value between two dates for various...

I'm with you now... Thanks for clearing this up.

Apologies, did not make myself that clear. Yes I have tried your solution and it works perfectly. Many thanks. I was just trying to understand your format argument in the format function "\#mm\/dd\/yyyy\#", particularly the back slashes.

Many thanks and take your point about the name, but it was only an example. I had tried with "Read_Date = #" & Format([Read_Date], "dd/mm/yy") &"#"), but with no luck. I guess the problem lies in getting the date format acceptable when passed over to SQL. Why do you need the back slashes as well?

Can't figure out why dlookup will not work for me in a query for certain dates? Simple example to highlight the problem: Table1 - Read_Date----Read_Value 31/07/14-------10 01/08/14-------20 03/08/14-------30 20/08/14-------40 Query based on this table with the following calculated field...

Have been working on a database file using Access 2010 64bit. DB was created under Access 2007 32bit on a colleagues machine so I had to add 'Ptrsafe' labels to Functions to allow it to run on my system. After I finished modifying the database, I removed the Ptrsafe labels and emailed it back...