Search results

In a blank column in the query design grid, type (verbatim): Upcoming_Birthday: IIf(CDate(Format([Birthday], "m/d") & "/" & Year(Date())) < Date(), CDate(Format([Birthday], "m/d") & "/" & (Year(Date())+1)), CDate(Format([Birthday], "m/d") & "/" & (Year(Date())) That's called a calculated field...

So in your table you have an autonumber field (which will change, by definition) and a field setup with an index to allow no duplicates OR, to allow duplicates - which is the case? My apologies, but I can't quite understand your ultimate purpose. Generally speaking, if your table is setup...

Hello and Welcome! Upcoming_Birthday:IIf(CDate(Format([Birthday], "m/d") & "/" & Year(Date())) < Date(), CDate(Format([Birthday], "m/d") & "/" & (Year(Date())+1)), CDate(Format([Birthday], "m/d") & "/" & (Year(Date()))) Criteria would be:Between Date() And Date()+10 The calculated...

Steve, I would pay attention to what Scooterbug has suggested. With different O/S's you're only asking for catastrophe with a shared db unless you split it to be FE/BE. Give each user their own copy of the FE. Databases corrupt in no time flat when they have to manage concurrent differing O/S...

You're welcome. All the best with your project!

Set Control Source for [txt_Days_Left_to_Completion]: = IIf(Date()<[Target_Date], DateDiff("d", Date(), [Target_Date]), "Already Completed")

Is the field data type in your underlying table Date or Text? If it's being stored as Text data, then first of all, I would change it to Date type. I would also change the name of your fields since "/" is a special character (i.e., [Tap Date_Time], [EV Report Date_Time]). Once you've changed...

Have you tried defining the parameters explicitly in the query - not just adding the form references to the criteria row, but also setting them in the Parameters list?

Hello and Welcome! Maybe I'm missing something, but why not just use the built-in DateDiff function and calculate your averages that way?

In order to break your date range into months you'll need to use an implicit SQL propagation technique by which the query generates records for each month. You may want to refer to this thread see how you would go about setting it up. Once you do this, you'll be ready to use a crosstab query...

VLookups can be frustrating, but they don't need an exact match. Anyway, for MS Query, you'd use something like this:SELECT DISTINCT [T1].[FieldName1], (SELECT Count([T2].[FieldName2]) FROM myDataList T2 WHERE [T2].[FieldName2] Like [T1].[FieldName1] & "*") AS NumberOfMatches FROM myDataList...

Welcome! why not just use VLookups?

This article might help you get your head around the security functionality of Access. Personally, I've avoided the Wizard and setup according to this article, which helped me to appreciate what is involved with the security features and how to plug the security "holes". Even so, there is a...

You could set an index on the underlying table requiring Unique values for the set of fields in question - then Access will automatically restrict a "duplicate" record from being saved (and confront the user with the relevant error message), if that was your ultimate intention. Otherwise, you...

Once a Select Case encounters a True condition, it executes the relevant code and then Exits the Select control structure. In other words, it's done, and doesn't proceed to test any remaining Case statements. Not sure if this was the essence of your question.

You're welcome Brendan, and all the best for your project!

Hi Brendan, No - you definitely need the variables declared in the function arguments. Try putting a <space> and an underscore("_") after each comma in the function declaration. This is the syntax for "continuing" your code statement on the next line. If that doesn't let you compile (but it...

In tblSeedMonths put a field for DaysInMonth (i.e., for Jan, DaysInMonth = 31, etc.), and if necessary, put a flag field in tblSeedYears to indicate which of them is a leap year in order to modify the number of days in Feb within the query. Presuming your purpose is something akin to finding...

I hear you. Loss of user interest due to a higher input threshold can be a killer. Sounds like this is a case where immediacy for the end-user trumps application efficiency for the developer ;) Well, cheers from across the "big pond" and all the best for your project Brett :cool:

Not to bedevil you now that you have a more-or-less finished product, but if you use a GotFocus pointer to callup the values for each displayed control into a single (or a select few) 'editing' control(s), this would limit your overhead appreciably - which in turn would make a Spin control...