M
Matt
Guest
I'm fairly new to DaDaBik, so whenever I've come up with an issue, I've gone through the forums and have usually found the answer. Failing that, I've gone through the php code and been able to find a solution. After several days of tweaking the interface, there are only two things that I can't figure out (I'll post a seperate topic for the second problem).
The issue I'm trying to work through is this: I have a field set as type "date". This is not a required field. In fact, a good percent of the 3000+ records in the database for which I'm using DaDaBik has no date. My problem is that when using field type "date," when updating a record or inserting a new record, the date field cannot be set or kept blank. It defaults to Jan 1st of the earliest date allowed by config.php. So new records with no date get the date set to jan 1st, and records already in the database that have no date get assigned a date of jan 1st once you use the "edit" feature to update the record in DaDaBik.
Is there any way around this (possibly a blank option above the numbers in the day/month/year drop down boxes)? Any suggestions? Thanks!
-Matt
The issue I'm trying to work through is this: I have a field set as type "date". This is not a required field. In fact, a good percent of the 3000+ records in the database for which I'm using DaDaBik has no date. My problem is that when using field type "date," when updating a record or inserting a new record, the date field cannot be set or kept blank. It defaults to Jan 1st of the earliest date allowed by config.php. So new records with no date get the date set to jan 1st, and records already in the database that have no date get assigned a date of jan 1st once you use the "edit" feature to update the record in DaDaBik.
Is there any way around this (possibly a blank option above the numbers in the day/month/year drop down boxes)? Any suggestions? Thanks!
-Matt