0

Date field does not remain empty

I have a few date fields that don't remain empty after I clear them.

Mac app 3.12.4

Only certain records show the behavior.

I clear the date and exit the database.  When I return to the database the date fields have the date:

Jan 1, 1970

In date field properties I have -  Required: no, Show in calendar: no.  Other combinations don't seem to affect the behavior.

Things I've tried:

clear the field in a table view with a double-click

use the clear function in the calendar popup

use a button script to clear the field with a null value

 

Has anyone seen this behavior?

 

Thanks

19 replies

null
    • Fred
    • 3 mths ago
    • Reported - view

    Wow, I thought this would have been fixed by now. Here is a post from a year ago with the same issue.

    I tried it out in 3.12.2 and was only able to reproduce it only on local stored DB. iCloud DBs do not have this problem.

      • spinner_7580
      • 3 mths ago
      • Reported - view

       Didn't run across that post... thank you for responding.  Yes this is a local DB but it is deployed online.

    • Mabel_Kingsley
    • 3 mths ago
    • Reported - view

    Hello,

    I thing you have to reach out to the support team of the Mac app. They can provide insights into whether this is a known issue, offer any workarounds, or escalate the matter for further investigation.

    • Leo_Woer
    • 1 mth ago
    • Reported - view

    I have exactly the same problem, and cannot find any places with a solution for it - and by the way mine is in icloud

      • Fred
      • 1 mth ago
      • Reported - view

      I still see the problem v3.12.8. Again only on local DBs, I don't have this problem with iCloud stored DBs.

      • Leo_Woer
      • 1 mth ago
      • Reported - view

       That is strange I also have 3.12.8 and stored in iCloud - I think it might be the way I clear the date field. Clear it by declare it false. Is there another way to clear it ?

      What is more strange is that if I create a new database, and just clear the date from the date window, it reacts correctly ??

      rgds

      Leo

      • Fred
      • 1 mth ago
      • Reported - view

       When you say declare it false do you actually use the word false? Have you tried null?

      • Fred
      • 1 mth ago
      • Reported - view

      Well I tried:

      In a local DB and with a button that sets the Date field to be null, it still shows the Jan 1, 1970 date.

      In an iCloud DB, with a button that uses Date := false (still weird for me to type), it clears the field and when I exit the DB and go back the field is still empty.

      • Leo_Woer
      • 1 mth ago
      • Reported - view

       Hi Fred - I guess that it has something to do with localisation neither null nor false gives the empty field in my iCloud

      • Fred
      • 1 mth ago
      • Reported - view

      I forgot that Ninox implemented Timezone Independent date awhile back. The iCloud DB that I have no issue does not have this feature turned on. I tested in another DB that has it enabled and I can reproduce the issue. Sorry for the confusion.

      • Leo_Woer
      • 1 mth ago
      • Reported - view

       no problem I will try to change settings

      • Fred
      • 1 mth ago
      • Reported - view

      sadly once it is enabled you can't go back. so if you have an old DB then it will be ok, but any new ones will have it enabled. But didn't you say you created a new DB and it didn't have this issue?

      • Leo_Woer
      • 1 mth ago
      • Reported - view

       yes when I used the CLEAR function from the date field itself

      • Leo_Woer
      • 1 mth ago
      • Reported - view

       I think I found the error - I created 2 fields a 'Date' field and a 'Date+Time' field, and it turns out that it is only the 'Date' field which has the problem

      I will report it now to the support team.

      rgds

      Leo

      • Leo_Woer
      • 1 mth ago
      • Reported - view

       

      I think I found the error - I created 2 fields a 'Date' field and a 'Date+Time' field, and it turns out that it is only the 'Date' field which has the problem

      I will report it now to the support team.

    • Mel_Charles
    • 1 mth ago
    • Reported - view

    Just for the record - I'm totally web based and I cannot get this error to occur.

    I presume you have tried Date:= " " too.

    and assume you don't have anything in the table triggers ( on new and on update)

    what happens if your force the Date to all zeros. Date := 00/00/0000 ? Does that hold up or do you still still leap to 1970?.  When I try this and return to the record I show an empty field  (i know its not really empty but .....but better than showing a spurious date

      • Leo_Woer
      • 1 mth ago
      • Reported - view

       yes I also Trier “ ”, have not tried 00/00/0000 - will try this and get back

      • Leo_Woer
      • 1 mth ago
      • Reported - view

        Hi Mel - have tried 00/00/0000 - it gives the same result, however, 

      I think I found the error - I created 2 fields a 'Date' field and a 'Date+Time' field, and it turns out that it is only the 'Date' field which has the problem

      I will report it now to the support team.

      • Leo_Woer
      • 1 mth ago
      • Reported - view

         yes tried it all - same result, but as I wrote no problem with the date+time field only the date field.

Login to reply

Content aside

  • 1 mth agoLast active
  • 19Replies
  • 143Views
  • 5 Following