Description: When a query is set up with calculations on a timestamp field, and the result set should be empty, Base complains of an SQL syntax error at the calculation. This errant error message is debilitatingly confusing, especially since there's no good way to do such calculations in Design View (which would a very nice improvement to base). Steps to Reproduce: 1.Set up an .odb file with a mySQL backend 2.Set up a query that uses calculations on a timestamp field (such as DATE_ADD()). 3.Arrange for it to produce an empty result set based on a Where clause on a boolean. 4.From the Edit SQL window for the query, click the "Run Query" button. 5.Observe the error message 6.Remove the Where clause that makes the result set empty. 7.Re-click the run button. 8.Observe the lack of error message. Actual Results: Confusing errant error message comes up when it shouldn't. Expected Results: Empty result set should be shown without error message. Reproducible: Always User Profile Reset: No Additional Info: In my case, the query SQL spans joined tables.
OK, I have a MySQL database and a table with timestamp field. What have I to do now? SQL-code will be helpfull, also a hint, what has been expected and what really happens and should be a bug.
Apologies. I made an awful mistake. I'm not sure how it happened, but I had somehow changed my SQL query such that it really did have an error in the syntax one time, but not the other. This bug report needs to be deleted. Can I do that as the initiator?
(In reply to Aaron Gerber from comment #2) > Apologies. > > I made an awful mistake. I'm not sure how it happened, but I had somehow > changed my SQL query such that it really did have an error in the syntax one > time, but not the other. This bug report needs to be deleted. Can I do > that as the initiator? I will this one set to WORKSFROME.
Thanks!