JenAAAA

OK, thanks for the clarification. That is good to know about the simpler way to search if one is using only Years. I am not entirely sure which way we might go on that. I actually just started adding in the modifications we discussed last week, where month, day, and year are all their own fields and then get combined later into a date. The script I posted is one I found on the web. As an aside, when you mention the StartYear and EndYear fields - are they just sort of built into the database without anyone manually adding them? Anyhow, thanks a lot!

My test database is working well but I am find that for the actual database I want to modify, that I would like to be able to search a range of years, which I would like to treat as numbers (not dates). Would you recommend using the following script in order to find a range of numbers based on 2 number fields (From_Year) and (To_Year)? (That said, I tried to build this script but FM did not care for parts of it). If( GetAsNumber(To) > GetAsNumber(From); GetAsNumber(From) & ¶ & NumRange(GetAsNumber(From) + 1; To); GetAsNumber(From) ) Or do I really have to make say those two fields date fields and use the script that worked above? Thank you!

Yes, thank you, it finally worked!! I tried going over and re-entering the raw dates into my Day, Month, and Year fields and suddenly it worked. I will keep at it. Thanks so much!

I will take a look at that, thanks! I did look into the actual calculation field, but it seemed like it did want to let me enter a date function besides that of Enter date - where it goes and grabs today's date. I will keep trying!

Hi, it's still not working for me. Two questions: I have all Month 1, Year1, Day1, etc. all set as Number fields. Is that correct? The other is that my field called Resulting Date is now a Date field and has a Calculated value under Auto-Enter. Is that the correct place to apply the calculation? The current result of this set up is a longer number (not a date) so I am not sure where things are breaking down here.

OK, I will try this. Thank you!

I set up those three different fields (number fields) and then tried to create a new field called Resulting Date. I gave that field a calculated value and specified the calculation to be: Month1 & "/" & Day1 & "/" & YR1 but it doesn't seem to care for that. The resulting number is far afield from what I was hoping to create. Any ideas?

Hi All, I am gradually getting a handle on things as I try to build up my scripts in order to get more functionality on the database i am working on, and appreciate the input I have gotten from the community thus far, so thanks for that! I have multiple questions but will try to hone in on a simpler one today. Is there a way to make a field be a date but not require it to be a 4 digit year date? For the type of records I am working (archival materials), each record has two date fields, Date 1 and Date2, and people entering metadata into the database can use those fields to reflect the span of time the archival object represents. However, we can often say that for the archival material we are working with, a specific date is not that clearly known, and if it is, is usually just a given year. I want the user to be able to search the database within a range of dates that they supply, and see what comes up. I have built a simple script that does that, though it is only looking at the Date1 field in the record, not Date2 (I haven't been able to figure that out yet). But the issue I am having is that I am not seeing a workaround if people populating the database don't know the 4 digit year date for either Date1 or Date2 for the object. I want them to be able to just enter a year, and I certainly don't want them to have to make up a month and day just to get the field filled out. Any thoughts? Thanks! Jen

Hello! I have two Date fields in my database, Date1 and Date2, that allow someone creating a new record, or searching for a record, to put a date in Date Field 1 and another, later, date in Date Field 2, so expressing a range of dates. The Date2 field can be left blank, it can be the same as Date1, it can be later than Date1, but it should never be earlier than Date1, so I want to build in a way to either stop the user from entering an earlier date in the Date2 field, or to at least warn them that they need to reenter the date correctly. I tried using Validate/Calculate and thought that might work, but it brings up a Revert Record message when the user makes a mistake, that I don't really want to happen. Is there a different approach that someone can recommend? I saw some reference to a piece of code called ObjectValidate or something like that, but have not found that value when I go into the Scriptmaking space. Thanks for any advice you might have! Jennifer