Search results

Why are you looking up a value you already have? Aren't you looking up some other field in the table? Edit: Sorry, I see pbaldy already ask that question

Cool - Glad you have it working

Group by cust id and max() the date?

Glad you have it working -

So you may need to check the references on the work machine. Not which one(s) you may need for the Outlook stuff. Perhaps Google it or do a search on this site.

Ok - so you're down to not being able to even opening a spreadsheet. What is the error message now?

Cool - Glad you have it working !

It could be it is opening but you just don't see it. Check if there is a option to view the outlook app object when it opens. Edit: For Excel it's something like: ExcelSheet.Application.Visible = True Not sure of the syntax for Outlook...

As long as the variable names are unique it should be fine to combine them... You put a DoEvents in after a section or command runs and the system is supposed to let if finish that part before proceeding to the next line. Probably won't help here but its worth a shot...

Have you tried a DoEvents? Can you put it all in the same routine?

I would copy the code to a new routine and remove everything but the lines required to open the workbook. Once that works start adding stuff back in... Sometimes objects persist if they are not explicitly closed. This can cause enumerated objects/references to get crossed up. Try saving...

1 - I don't see a recordset update (If that is required) 2 - Have you stepped through the code? Sometimes the issue can be realized by doing this...

Sounds like you need to group on these composite key fields in a second query, concatenating the other fields. ?

Too slow this morning...

Loop through the OpenReport 10 times?

Not sure I understand. You mean from one record to the next?

Seems like you could just subtract date 1 from date 2 and if the difference was greater than 1 - bingo...

What version of Access are you using? I'll cobble something together... Edit: See if you can open this -

In short the logic is starting to get a bit more complex than the table/field validation feature can manage. So yes, create a vba routine that checks the date before it allows updates. Have you done vba before?

I would move this to the form and cancel the update event if the tests fail. I like putting all of this type of validation in the presentation layer so the data layer is more portable. Also narrows down areas to poke around in when trying to figure out how it works down the road :) Hope that...