Sage 100

Timecard Report. Error 11 SYDATE line 41010. Dump shows no TC1 info. No ACCESS. Tried Crystal, dates all look OK for 06/08 and 06/09 which are the dates that give the error. 200 records to go through individually - is that my only option?

Sure that line number is right? What version?

In TimeCard Entry try searching by date

I did search by date. They all look OK. They have about 150,000 records so it takes forever, but nothing looked bad in the dates. Version 4.4.0.5 I'm working on narrowing it down by department, which is taking forever. The TC report takes about 5 minutes to run each time I run it for a department for the date/job. Ooh, I just got a new error on one of my reports. Off to go look it up - error 57 (?????) SYDATE line 1625.

Ah, same entry in the KB. Poop.

GREAT

I don't see line 1625 in the code - it jumps from 1620 to 1630 - no 1625

Still curious about the line on the error 11 - 41010?

Do they have VI? If so, try exporting that field into a CSV file, then searching for some crappy entry.

line 1600 starts the section called ""Return Raw Time in HHMMSS Format"" - maybe it isn't date but time

Oh now THAT wouldn't surprise me. They have had issues with the time format from the file they import FROM. Great, gives me something else to look at, because those darn dates looked sterling. THANKS!

If you go into the SOTAMAS90 ODBC and click on the 'null date' under the options tab, it will let you run the report, or export to excel with a bad date.

@RobertaFerguson - HUGS AND KISSES - I found the error and it IS a time field, not date! THANK YOU THANK YOU THANK YOU!

I have a client that uses Timecard extensively. When we have a SYDATE error, it almost always invalid Time In/Out data

Yes, the client apparently had this error before and thought it was fixed.... Instead of 0 as midnight, other system is giving them 24.

What was the original line number for the error. 41010 does not seem correct - that line does not exist in any SYDATE program I have.

It really was that line, but man, that line doesn't look like any line number I've ever seen, actually.

My errors generally point to Error 11 SYDATE Line 40120