tag:blogger.com,1999:blog-3546795444588179926.post7890975151225826177..comments2024-03-28T18:41:34.786-07:00Comments on Alex on DAX (Alex Kwitny): Database log throws error "Error executing code: Wrong argument types for comparison."Alex Kwitny (Kwitwell.com)http://www.blogger.com/profile/12458072273859749789noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-3546795444588179926.post-47528602984505464772023-06-17T08:15:17.675-07:002023-06-17T08:15:17.675-07:00Very nice blog you have hhereVery nice blog you have hhereSadiehttps://ciderfireandbooks.blogspot.com/noreply@blogger.comtag:blogger.com,1999:blog-3546795444588179926.post-64246734435707904832012-10-19T09:53:08.022-07:002012-10-19T09:53:08.022-07:00That's strange. I'd guess you might have ...That's strange. I'd guess you might have had added a custom string field to a table, typed some data, then changed the string field to a float. You would receive a synchronization warning that says "Warning this field will be dropped and recreated" or something to that sort.<br /><br />All is well, except that if you had DB logging turned on, that string field was recorded in the DB log, then it is now a float and it is a type mismatch. This would explain your error, but it's just my guess.Alex Kwitny (Kwitwell.com)https://www.blogger.com/profile/12458072273859749789noreply@blogger.comtag:blogger.com,1999:blog-3546795444588179926.post-70910701186053762312012-10-19T01:42:51.306-07:002012-10-19T01:42:51.306-07:00I just had a case where I got a string value (Cust...I just had a case where I got a string value (Customer or Vendor ID) in the log for a custom float field on InventTable. AX 2009 from the start, apparently you don't need to upgrade to get corrupt data in DatabaseLog.Anonymousnoreply@blogger.com