Subject Re: (no subject) From Andy Taylor <andy.taylor.1959@outlook.com> Date Thu, 01 Apr 2021 10:11:24 -0400 Newsgroups dbase.getting-started Shannon, I don't have Mervyn's patience so I knocked up a table with values and put dates in it including 2026. Then I did "sum" from the command window. All records were correctly summed including those with dates in 2026. This simple exercise tells us that there is no specific bug in dBASE concerning dates in 2026. What is happening at your end is very odd and in my view is very likely to be down to the code being used to put relevant data into "scope". Your 2026 data is just being excluded somehow. As Mervyn has suggested please attach your test form and (small) test data file to your next post. Regards, Andy P.S. An unwritten rule is that no-one here mentions each others stupid gaffe's - if we did we'd be talking about nothing else. > I feel like an idiot for leaving the subject line blank... > > I did the tests with regular dBase code, xBase and SQL in a regular Query and had the same results with all of them. I tested old and new tables and forms, all the same. I even tried to include only the dates with that year specifically using a FOR statement. The records are read and displayed correctly in a grid or using the print command. > > > Shannon Lee Alberts Wrote: > > > I'm using dBase 2019 with level 7 tables and my employer uses version 11. The epoch is set to 1950 and the dates are read as dd/mm/yyyy. We use the .dbf files and store them on our own server. > > > > A summary of the problem, all records display correctly but when using a simple function like SUM, the records with the year 2026 are not counted, even though there are no conditions or filters that would trigger that. My co-workers told me that this has been a problem for a while already. > > > > I'm new to the company and to dBase but my employer who has been working with dBase for years says he has not been able to trace the fault. The executable we use has over 600 forms and reports and this issue seems to occur in each and every single one of them, even the new ones. > > > > I created a "dummy" form and a .dbf to test if it is just that project but it seems to do the same. I played around with the date and it is only the year 2026. It includes 2027 and up. > > > > I was told this is a bug which is why I previously put it under that topic, sorry. >