Search results

First, your report footer says "Total number of paid members who paid for the month" suggesting that the report is for a single month. The detail lines show several different months with at least one person paying in two of those months so any totals or percentages will be misleading. Is the...

I get the feel of what's going wrong i.e. it's going into that module to work out a Child's age even though the Soldier doesn't actually have a Child. I think I need the database to get to the root of the problem.

I don't think the problem lies within the form but in the the report. In which module is the "failing" code? (Given the UK forecast for tomorrow, I think I'll be available here most of the day!)

Sorry if I'm stating the obvious but the problem lies within the data / code behind rptRecordPrint. Try working on that direct rather than invoking it via your command button i.e. put the report into design mode then go into print preview mode. If you're still stuck, post the database up here...

A fine contender for the January "Golden Spur" award. I would never have suggested that myself, of course :D

I've often found that other DoCmd's relating to record operations aren't always as clever as you'd like them to be. There must be a VBA-checkable property that would tell you that the form / underlying recordset is in "new record mode" but I don't know what it is off the top of my head.

You're welcome. It's often difficult trying to explain / understand detailed technical problems first time when all you've got is a screen & a keyboard and you have no idea of how savvy the other person is!!!

Using record ID 1 from your data example: The outer FOR loop first looks at Col1 (well, it would if I'd started at 1 instead of 0!) which has value A, then the inner FOR loop cycles through Col2, Col3, Col4 and Col5 (but should have started at 2, not 1), zapping any of them which match Col1 -...

Maybe it's already in "new record" mode because the underlying table has no existing records?

OK, gotcha now! Try this, with single quotes around TEXT(ROW([A17]),"-0") SELECT tbl_transaction_details_b.SHIPTOCUSTOMERNAME, tbl_transaction_details_b.SHIPTOADDR1, tbl_transaction_details_b.SHIPTOCITY, tbl_transaction_details_b.SHIPTOSTATE, tbl_transaction_details_b.SHIPTOPOSTALCD...

You could use the Fields collection indexed by field numbers in a double loop to pick up the contents of each field and compare it against the contents of each subsequent field, zapping any subsequent matching fields. Something like this: set td = currentdb.tabledefs("tableName") set rs =...

Ah! TEXT and ROW are Excel functions, I've never seen them in Access.

I don't think you can do that with a simple query export. You'll need to either a) set up an Access report looking like the Excel template and using the query's data, or b) write some VBA code to get the data from the query into the correct bits of a template-formatted Excel file. Good luck!

I can't even open the unzipped database! Access tells me that it's an unrecognised database format, even though it has a .accdb suffix.

Go into SQL view, copy the whole query and paste it here. Someone might be able to help if they can see the whole picture.

Yep, I've fallen for that in the past - report sequence property that (quite rightly) overrides the query's own sequence.

Run the query native i.e. outside the report. In which sequence does the data appear?

Is this a one-off exercise? If so, in the master database create linked tables to the tables in each of the child databases then then use queries to append the child data to the master data. No need for VBA.

You don't need the UNION: SELECT [Transactions Extended].* FROM [Transactions Extended] ORDER BY [Transactions Extended].[Income/Expense] DESC

I get the same error if I added even the simplest of code to the Load event of any of your forms but I have no idea why! If however I created a new form and gave it a Load event all was fine. I copy/pasted all the controls from WelcomeNote onto my new form and it was still OK, coming up with...