Hi,

 

If I use "Get (CurrentDate )" in a Field Calculation for each record …  will it get the current date when the user starts the file up ?? Each Day ?? Or will it only get the current date once ?? When record is created ??

 

If ( not IsEmpty ( Invoice Paid Thru Date ) and Agreement Billed 1  ≠ 1 and Invoice Paid Thru Date - Invoice Alert Value  ≤  Get ( CurrentDate ) ; 1 ; "" )

 

Here is why,

 

I am using this "1" to build a relationship … 

 

When I use a Global Fields in the calculation to hold the CurrentDate ...

 

Filemaker does not allow me to select "INDEX".

 

Without the "INDEX" check box checked, the relationship does not build.  And the only way I can select this check box is to "UNSELECT" "GLOBAL"  ...

 

So, I replace the Global field with "Get ( CurrentDate )"

 

 

Hi,

 

I've tested and found out that the "Get ( CurrentDate ) does not get the current date after record is created.

 

HELP !

 

I need at DATE Field that updates when the file opened on my "Table" so I can use it in my calculation to build a relationship.  Using a Global Fields Works … meaning I get the "1" but filemaker will not allow the relationship because the Global Field can't "INDEX".  

 

Please see above calculation ..

 

Thank you.

 

 

Tom :-)

[email protected]

Perhaps use an auto enter instead of a calculation. Auto enter by calculation using Get(CurrentDate) and you can store it as well. No need for global.

Hi Rick,

 

Nope, didn't work.  Tested it, though I think auto enter is for when you create a record because the field is empty on my layout.  I restarted the file and the field is still empty.

 

I need a field that updates on startup that is not global.  Now I can build a relationship to a "ONE" record "TABLE" and on start up "SET" the DATE field to the current date but Filemaker will not allow me to "INDEX" any calculation on another table that references the "RELATED" fields.  Huh

 

Any thoughts, guidance, I would would be grateful.

 

Thank you

 

Tom

A Foreign Key part of a relationship can not be based on data that can change, hence the reason that you are having problems with the index. 

 

I’m having trouble getting my head around your structure and the purpose of your script.

 

Why not post a copy or a demo of your file?

In a nutshell: if the calculation field is stored, the date will not update. if it is unstored, you cannot use it as the matchfield on the "other" side of a relationship. That is why your method cannot work. Why don't you describe the problem instead?

Lee, Comment;

 

Never mind, I see my mistake. ( Trying to explain it to Lee, I realized me error.  Thank you Lee )

 

I build a lot of relationship with "1's" and was not paying attention.  All I needed to do was build my relationship using my "DATE" fields on both tables.

 

Sorry everybody.  Oops!

 

Tom :-)