Are you saying to implement this idea in all of your code? That I"m not sure, I'm with Norie in terms of, there is too much Select and Activate type of thing. It is very very very preferable to avoid that and just take action on objects. I was just commenting on this discussion about finding the last used row, and I was soap-boxing my oft-repeated warning to avoid UsedRange or any similar thing.

But based on your recent post which already knows what it wants to do in plain english. So can't you just do the loop and repeat it 700 times?

voila ! I'd be happy to do that, but I can't get the syntax to work !

Steve

Ok, so what do you have so far? and you want to go down to which specific row?

Ok, so what do you have so far? and you want to go down to which specific row?

700 would be good for now

Ok, let's try this first, using 99% of your original code, but with a change about the lastrow. I just want to qualify this solution by saying, due to time limitations I'm not writing this in what I think is an idea way. I'm sort of leaving most of the Select, etc., in place. (IMG:style_emoticons/default/frown.gif) But I believe it should work "most of the time", as code with Select and Activate is liable to work.

Isaac,
that worked like butter - took like 3 seconds to run..... I tested the dates - my next 'upgrade' is to make the report code (col F) more dynamic in a couple of ways:

First of all, instead of all these hard-coded dates, will have like cur date minus 14 for weekly reports let's say, and at the same time cur date - 59 days for monthly reports, cur date minus 4 for daily reports

so....

If:

Frequency (Col H)........ Last run date (Col G)>>>>>>>>>>>>>> ACTION TAKEN
--------------------..........------------------------ .......................................................
Daily/Weekly/Mnthly................... <null>..........................................go to next cell
Daily....................................< cur date - 4...................................... Type "A" For active in col F if TRUE, "D" in Col F if FALSE
Weekly....................................< cur date - 14...................................... Type "A" For active in col F if TRUE, "D" in Col F if FALSE
Monthly....................................< cur date - 59...................................... Type "A" For active in col F if TRUE, "D" in Col F if FALSE

But in the meantime, I celebrate !!!!!

Thanks so much !!!! (IMG:style_emoticons/default/cool.gif)
Steve

Glad to help

You could do that with a series of If statements and use Offset to put the values in the cells as appropriate.

Something like this rough code.

Basically that goes through all the rows in column G.

If the value in the cell is empty or not a date it moves on to the next cell.

If it isn't empty and contains a date then it puts 'D' in the the value is less than TDATE, and if it's greater than TDATE put's an 'A'.

Like I said the code is rough but I hope it makes some kind of sense:)

norie,
I know this was just a rough example, and I can follow your lead, but was this supposed to do anything ? ( It doesn't - I attached an example )
Steve

Since column G isn't always going to be fully opulated use another column such as A.


That does do something - it puts 'D' in F1 and 'A' in F5.

Oops, forgot to add a check for G9 on 'ListNotes'.

Add this just before the For...Next.

still nothing
(See attached)

How exactly are you running the code?

I've made a few changes, mainly to make sure the code references the correct worksheet(s) and adding a couple of declarations.

File attached.

here is what I dont understand.

When I provided that original code in response to another thread, you said it was working exactly as you wanted. AND, it worked as tested. That included the "A" and the "D", what changed in your spreadsheet?
Code just doesn't stop working unless something changed to the environment.

EDIT:

Other thread.. http://www.UtterAccess.com/forum/Evaluate-....html&st=20

Bob

Which code, in this thread, do you mean by 'that'?

Norie,

The first post. The original version is mine. Which was provided in that other thread. Some techniques, good or bad, are easy to tell the author of.

Bob

bob - I honestly don't know - I'll just throw my hands up and say operator error - sometimes I put some code to use, and I see exactly what it (the code) is doing - other times, I'm not following the process - there was at least a couple of things going on I didn't understand - that was the case here where in trying to 'enhance' my code, and add functionality, things got 'broke' - for example, someone might give me a line of code as a solution, thinking, let's say that I'd know it was to REPLACE another line of code or 2 or 3 lines, and I just added it - just a hypothetical there - so not sure :-(

Anybody try the code in the workbook I attached?

well as long as this conversation is still active, let me add my question to the list of tomatoes being thrown in Steve's general direction - LOL, I'm just kidding - so Steve, the code I last posted , which was basically Bob's except I just added the # of times to loop - didn't you say it was working ??