Search results

Don't do anything. I'm sure it's doable, so I'll get back to this one way or the other tomorrow when I'm rested.

No they do not. Let's see what the actual issue is.

#5445 Explaining complexity with something even more complex is contrary to the ways of science. And this even more complex complexity then becomes the irrational and the irrefutable and the unarguable, a.k.a. faith. Oh yeah. This "complexity" is still behind - created the world as we know it...

To solve this: do not muck about with current record set. Apparently even Access got confused and did not know where it was. Now, wherever I could I changed to Recordsetclone instead. Also, in On Current, need to do Recordsetclone.MoveLast to get proper recordcount. Now it seems to work...

MoveUp still not disabled. 1. Open the db 2. Click anywhere in third row from bottom 3. Click MoveDown 4. Click any column but first, in the new (=last) row MoveUp is still enabled I have no understanding of what is happening here,which is why I cannot, offhand, fix this!

Perhaps. But honestly, if your programming experience is limited then do not waste your time. Making sure the code works will in such case take longer than simply preparing and running 52 queries.

Before I attempt to digest all this (and it won't be now) how is all this dealt with today? Your company exists, and functions. presumably, so there must be one or more workflows. If you want proper help, present the workflows, rather than letting us reverse-engineer them from what you...

Not crit1 crit2 crit 3678 but MyCriteria= crit1 & crit2 & crit 3678 OpenRecordset ,,,,MyCriteria,,. (count the commas yourself, this is an example)

AFAIK MS changed the default sequence of reference libraries. Meaning, in 2007 an ambiguous Database or Recordset defaults to another library than in 2003.

Your coding is a mess, but I guess you know that. Do not persist using the default names like Text376 , but name each control according to what it is. When you return to this in 3 months - and you will - you'll thank yourself. AS to your criteria: there is no reason to do it in two places like...

You need to disambiguate declarations. Recordset-> Dao.Recordset DDATABASE -> Dao.Database

Was there a change? When I click in new row in some column, MoveUp is still enabled. Anybody is welcome to chime in.

Also, you'll be much better off using short names, consisting of letters only (no spaces or non-alpha), for all you object and field names

I have an A2010 form with a MoveUp and MoveDown button. A click will move the last record I clicked on, up or down. When on new record, both buttons should not be enabled. If I select a record by clicking in it and I click MoveDown until MoveDown is disabled, I wind up in the last record of...

What did you do exactly. NOt a story but show your attempt

@Uncle Gizmo We are not looking forward to your resignation, but the UK monopoly on Colins has obviously been broken :D

You do need an append query for each column of your budget. However, if you can manage to get the spreadsheet in as a staging table or link to it as such, with the date as column name, then it should be easy to make some VBA that runs through all columns and runs a query for each. Update: If...

Put [] around the subform name. And do not use spaces, or - or any other non-alpha characters with the exception of _ in names in the future.

SO what expression did you enter for the button? (BTW Listing snippets only is a bad bad habit)

Within quotes everything is taken literally. "*[abc]*" looks for everything that matches the literal [ and a and b and c and ] So by the way, the criterion was working just fine - delivering the nonsense exactly that you asked for :D