Search results

Suggest try it and see

A quick review - now I can see what you are trying to do, I think the solution is to use a union query - you will need 2, 3 or 4 for each table. one for the data, one for the total and perhaps one for the heading e.g. 'Grouping Title for Sub-report 1:'. (Which seems pretty meaningless to me...

perhaps capture the recordset.absoluteposition property value and on return set it dim currRec as long currRec=recordset.absoluteposition ... do stuff recordset.absoluteposition=currRec if you have deleted what was in the absolute position, it should go to the next record you'll need code...

Assuming you are committing to cancel or save during the life of the open form - For single forms comparing oldvalue and value is probably sufficient since data isn’t saved until the record is updated (form update event or forced with dirty) For continuous forms consider using an ado...

I use this code to import transactions downloaded as an excel file - I've simplified it as it looks up various parameters Private Sub btnImpTrans_Click() Dim sqlStr As String Dim fPath As String Dim db As DAO.Database 'look in download folder to select file (Transaction was dlookup, now a...

Build it in the QBE to get the bracketing correct Based on your original query you don’t need tstnum in your join as statename is unique

One main form, one subform and in the subform control properties, set the link child/master properties to set the filter

Depends if there is a time element in your data - but it is a fail safe if you are not sure, You also don’t use quotes around dates in access sql and you don’t need to specify zero time for the start date I tend to use the >= and < method where the enddate is enddate+1 WHERE TransactionDate...

can't really help without seeing the data/queries - and not clear what your final report is supposed to look like with 6 subreports. Your sql would appear to not have enough joins Would also help if you aliased your queries and not use spaces in table names - makes the sql much easier to read...

without knowing what you have or what it looks like, possibly, you'll have to try it but I think the issue is with outputting to html - the use of an 'oversized' subreport causes the issue. So if you can avoid subreports (or at least those that potentially can 'oversize' by combining into the...

just got back - this is what you should have - in green

No - it’s already there - 2nd column if I remember correctly (I’m on my phone). In report design view on the ribbon you should see grouping and sorting options

Reports ignore the sorting in the recordsource- you need to do the sorting in the report

See the example db I attached

total number of pages is 437 -see attached I did this per my suggestion on the other thread of simply removing the subreport, adding the other table to the recordsource and copy/pasting the controls from the subreport to the main report. The only difference I can see from a brief review is the...

Just to cover other bases, I would also check the controlsource of the controls are specified

Many years ago a client decided to implement a well known online crm system. I was involved with integrating it with finance, commissions and hr systems. I discovered that if you knew the login details (of a sales person for example), you could not only access the data from excel, that access...

Yes - and knowing that, there are steps you can take to prevent it - not saying how as a potential hacker may be watching 😀 and it can start be hacked but further up the difficulty scale How secure you want to make it depends on your security requirements. No system is totally secure - even web...

It is likely your new boss will want a 'rolling' view of currently active products If you add an inactive flag, I would make it a date rather than a yes/no field. That way you mark as 'inactive over two years go' with a date two years ago, 'inactive in the last two years' with a current date...

I will be interested to know how you will manage your provision of information accessed by a hyperlink and how you expect them to update the data around product recalls etc.