I'd open Manage | Database | Fields, find this field and double click it to bring up the field options dialog so you can check the auto-enter options for the field.
I'm guessing here that you have it set to auto-enter the creation or modification date or possibly you have a calculation that uses Get ( CurrentDate ) to enter today's date.
Thanks for your effort Phil. I don't want it to enter the current date - I want it to enter a future date of my choice. Are you suggesting forcing the field to enter the current date first, then I click into it to enter a future date?
Thanks for your clarification.
No, it sounds like that's what you already have specified and needs to be changed so that the current date is not entered.
Thanks for your clarification.
The field of concern is a simple date field with no auto-entries, field script triggers, layout script triggers, or calculations, etc. that might prompt the date to revert to the current date after I've selected my desired date.
However, the field is a match field between the Client and Test tables. This particular table occurrence ("Upcoming Tests") is looking for dates > or = the current date, a global date on the Client table. By definition, a record in this portal must have a date, and to remain in the portal after I exit, it must meet this criteria.
Maybe because I'm typing into a portal that requires a date, FileMaker is selecting a date that matches the criteria (>= current date). Thoughts?
This is due to the field being a match field in a relationship where "Allow creation of records via this relationship" is enabled.
What's the exact relationship you've defined here and why?
Clients::globalDateFIeld > Tests::DateField AND
Clients::ClientID = Tests::ClientID
If this is the relationship, it's auto-matically entering the contents of your global date field. If you put the desired date in the global date field first, you can create the related record with out entering any date in DateField at all, you can just enter data in another field in the portal row. That might not be the optimum solution here though. Tell me more if you want to discuss alternate approaches.
Thank you very much. You are absolutely right. The relationship between my client table and a test table occurrence called NextTest is as follows:
Client::CurrentDate(global) <= NextTest::Scheduled Test Date
Client:ClientID = NextTest:ClientID
I was using the portal for two conflicting purposes: 1) to display the test dates that are scheduled in the future and 2) to create new test records with dates greater than the matching current date field.
I understood the unique key field in my parent table would populate the child record's foreign key upon record creation, but it didn't occur to me that other matching fields would do the same thing when "allow record creation" is checked. That's a great feature to send a lot of data to a child record, but I wasn't using it properly.
I will move the record creation function to another portal that doesn't match by date.
Thank you for the new insight, and for understanding my problem long distance!!
Since you are using FileMaker 11, you might just use a portal filtering expression to filter out all but dates for today and later.
Get ( CurrentDate ) < NextTest::Scheduled Test Date