I have tried to set up checking duplicates on one field only, the CEMS field which is patron account number.

When ever I set it to check for duplicates it comes up with a duplicate record found every time. Even when I take a test card and search for the test card number, and delete all of the test card results.

My goal is to have it check the CEMS field only and find duplicates on a per day (24hour basis) one card number per day allowed..

Another issue I am having is with timezones, we are in washington state, pacific time zone. but our business day runs from 7:00am - 7:00am, I have found if i change the system time on the MySQL box to the Japan Timezone this works, the problem comes when trying to update our intranet website, with the differing timezones..

I have tried unsuccessfully to change the time zone in the [mysqld] & [mysqld_safe] sections of the startup INI file. When I try to force MYsql into the japan time zone the server fails to start and an error message pops up failed to start unexpectedly, etc..

I've tried that,I have all the fields set to no on duplicate checking except one, the CEMS field.

Still comes up in DaDabik with this response:

"Duplication is Possible... this record appears similar to....."

This happens everytime a new record is inserted, no matter what the CEMS number is.
Even if I use a test card where I know what the CEMS number is, and I do a full search for that number before hand and remove all entries containing that number.

The CEMS number is inserted via a magnetic card reader from a patron's membership card.

The CEMS number itself can be an 8-15 digit number.

My hope is to check for duplicates on two fields, Date & CEMS..But from what I have read in the forums this is not possible at this time.

I am on vacation at the moment and will be back at my desk on the 25th of February.

I will be checking my email from time to time and I look forward to any other suggestions you might have.

Have you tried to adjust the percent similar option in config.php? Try setting the duplicate checking to 100% which would tell the program to flag on absolute duplicated entries in the cems field. That usually works best if you are dup checking on fields containing any type of id/card number.

Debbie
(Latest version of DaDaBIK when this message was posted: 3.1 Beta)

I'm not aware of limitations on the number of fields that you can check duplicates for. Have you set both fields to check for dups? In the interface configuator, there is an option for every field in the db table that you can tell the program to check for dups.

Glad things are working otherwise!

Debbie
(Latest version of DaDaBIK when this message was posted: 3.1 Beta)

I had another thought with your dup checking on the date field. It should work if you have your db date field set to date only and not datetime. Since you want to check against dates, you don't really need the time stamp with it. Try setting the field you want to check against to just date and see if that works.

If you are checking for dups on a datetime field at 100%, it will never work because the time changes every second.

Debbie
(Latest version of DaDaBIK when this message was posted: 3.1 Beta)

I turned on dupe checking for the date field.
It does not seem to make any difference, the exact match on the CEMS field still works.

I also tried making an entry with todays date, then going into MySQL and editing that row of data and changing the date to yesterday..

When trying to reprocess the same test entry for today all over again, it flags the CEMS field as it should, but seems to ignore the date entry and and lists the modified row with yesterdays date. If the DATE & CEMS field checks are turned on, it should, I would think check for DATE & CEMS on that rows data into the table.

But it does not seem to work that way..It seems to check down the field columns, instead of across the table field rows.

In Dadabik I have the entry field set for an insert_date field, and in the MySQL table I have it set to DATE (9 chracter legnth)so the minutes and seconds are ignored and never entered into the table.

One other minor thing is when the duplication is possible page pops up it does not display the data from the linked table on the duplication table page. If I click the icon for details it does however show the linked table data. I find it puzzling that on all other "screens" the linked table data is displayed in the big table view except during that duplication checking view..

> I also tried making an entry with todays date, then going
> into MySQL and editing that row of data and changing the date
> to yesterday..
>
> When trying to reprocess the same test entry for today all
> over again, it flags the CEMS field as it should, but seems to
> ignore the date entry and and lists the modified row with
> yesterdays date. If the DATE & CEMS field checks are turned on,
> it should, I would think check for DATE & CEMS on that rows
> data into the table.

Confused ... if you want date checking on the field for the same date and you enter a new record for today's date, why would it flag the record with yesterday's date? Yesterday's date is no longer a match to today.

> But it does not seem to work that way..It seems to check down
> the field columns, instead of across the table field rows.
>
> In Dadabik I have the entry field set for an insert_date
> field, and in the MySQL table I have it set to DATE (9 chracter
> legnth)so the minutes and seconds are ignored and never entered
> into the table.
>
> One other minor thing is when the duplication is possible
> page pops up it does not display the data from the linked table
> on the duplication table page. If I click the icon for details
> it does however show the linked table data. I find it puzzling
> that on all other "screens" the linked table data is displayed
> in the big table view except during that duplication checking
> view..
>
> Thanks,
> Samuel

Is this installation located somewhere it can be viewed? If so, send me the link via private email message and I'll check it.

Debbie
(Latest version of DaDaBIK when this message was posted: 3.1 Beta)

> Confused ... if you want date checking on the field for the
> same date and you enter a new record for today's date, why
> would it flag the record with yesterday's date? Yesterday's
> date is no longer a match to today.
>

I belive it it is catching the dupe on the CEMS field, and showing all records with that number, instead of by DATE & CEMS.

>Is this installation located somewhere it can be viewed? If so, send me the link via private email message and I'll check it.

No, it is not it is installed on our intranet for internal use only..

I can send you any config files or do a dump of the MySQL layout if you like..

> Debbie,
>
> I turned on dupe checking for the date field.
> It does not seem to make any difference, the exact match on
> the CEMS field still works.
>
> I also tried making an entry with todays date, then going
> into MySQL and editing that row of data and changing the date
> to yesterday..
>
> When trying to reprocess the same test entry for today all
> over again, it flags the CEMS field as it should, but seems to
> ignore the date entry and and lists the modified row with
> yesterdays date. If the DATE & CEMS field checks are turned on,
> it should, I would think check for DATE & CEMS on that rows
> data into the table.
>
> But it does not seem to work that way..It seems to check down
> the field columns, instead of across the table field rows.
>
> In Dadabik I have the entry field set for an insert_date
> field, and in the MySQL table I have it set to DATE (9 chracter
> legnth)so the minutes and seconds are ignored and never entered
> into the table.

I don't know if this can help, but maybe there is a misunderstanding on the way DaDaBIK performs the checking prcedure.

If you set "check for duplicates" for more than one field, for example two, DaDaBIK, for each of the two fields of the inserted record, checks for duplicates against all the pre-existent records, comparing each field content with the two fields of the pre-existent record.

> One other minor thing is when the duplication is possible
> page pops up it does not display the data from the linked table
> on the duplication table page. If I click the icon for details
> it does however show the linked table data. I find it puzzling
> that on all other "screens" the linked table data is displayed
> in the big table view except during that duplication checking
> view..