Search results

amend the source report in acces?

How about creating a report and printing it to a PDF printer?

allowing the month to be chosen and forcing the year to NOW, will not always work. I.e. on Jan 1st you will want to see last year's december data.... I suggest allowing the year to be chosen as well or atleast think about it. How did you fair implementing this?

Almost, you cannot make a full X = Y in one where clause like that. Instead you create an (invisible) field X and put Y in the where clause. i.e. put Year([Request]) as a field Year(now()) as the where clause

What else would you need but to TransferSpreadsheet? In your qryRequirements you can easily "where QueryMonth = Yourform!SelectedMonth" and all you need is to export it?

Inner join is the same as a join, depending on if access accepts it or not... You can add -2 -3 -4 -5 to the join(s) to ensure you find results... Or even do a Max(readin) join date between today -1 and today -7 I do agree, performance probably wouldnt be an issue on such a small set.

With all due respect to the suggestions posted, but No no no and once again no.... Dmax and Dlookup should be avoided like the plague and inline subselects are as bad as those two. Assuming you take a measurement EVERY DAY, a simple self join can do the trick. Building on what @MajP posted, it...

Total gamble, the comma is the column seperator. try replacing out the comma for a semi column or pipe simbol, see if that helps.

Yes it can using the HTTP object ... One example can be found here: http://excelerator.solutions/2017/08/28/excel-http-get-request/ If you prefer Youtube:

mid&([Site].[map_ref_numbers],6,5)) Shouldnt that be mid$([Site].[map_ref_numbers],6,5)) or even mid([Site].[map_ref_numbers],6,5))

why create a table in the first place, you seem to be able to get the data in a query duplicating the data by way of a create table query is a seriously bad idea...

You can also make things relative.... i.e. Your db exists: C:\Program\DB\FrontEnd\YourDB.accdb Your BE exists C:\Program\Tables\Backend\YourBE.accdb assuming the relative path stays the same ..\..\Tables\Backend\YourBE.accdb you can relink them as wel. Assuming you have the BE on a server...

Strike that reverse it.... Make your form unbound and add a "save" button, prior to saving your data you can check what you are adding, if nothing then ... dont save it. Also you can add a "cancel" button this way the user can opt not to save at all.

Thank you for essentially retyping my earlier post :)

main form or subform shouldnt make a difference. Likely you skipped a NZ someplace for your subform.

Months should not be columns, they should be rows as a result you wouldnt have this problem. What you are doing is seriously flawed in design.... re-design should be a real option. Given your problem though, You are doing probably JAN + FEB + MAR, eventually one of the fields is blank (AKA...

The formula, ok, takes some creativity, but this seriously?

Is the reverse and sure looks simpeler :)

I have a dutch version but this will do the trick: =LENGTE( SUBSTITUEREN( SUBSTITUEREN( SUBSTITUEREN( SUBSTITUEREN( SUBSTITUEREN( SUBSTITUEREN( SUBSTITUEREN( SUBSTITUEREN( SUBSTITUEREN( SUBSTITUEREN(A1 ;0;"")...

UNC paths or "check" for the different options on startup of the front end and relink your tables.