ACC2000: Using Hijri Dates for Criteria in .adp Files Results in Error Message (232064)
The information in this article applies to:
This article was previously published under Q232064 NOTE: This article discusses complex scripts functionality. Complex scripts functionality is available when you use the Office Language Settings tool to enable a language, such as Arabic or Hebrew, that requires this functionality. For more information about multilingual features, click Microsoft <I BRACKET="YES">your Office product</I> Help on the Help menu, type multilingual features in the Office Assistant or the Answer Wizard, and then click Search to view the topics that are returned.
Moderate: Requires basic macro, coding, and interoperability skills.
SYMPTOMS
If you try to run a criteria that contains Hijri dates in client/server databases, you may receive error messages, and then the operation fails.
CAUSE
Date criteria in client/server databases is handled as Gregorian. A Hijri date entered in a criteria expression is interpreted as Gregorian, and this results in an "out-of-range" message because Hijri dates fall below the minimum Gregorian date allowed by SQL server. Using the alternative method, CDATE("hijri date"), doesn't work because SQL server does not recognize this function.
RESOLUTION
Enter only Gregorian dates in criteria. If the database calendar is set to Hijri, use the Gregorian equivalent of the target date in the expression.
Modification Type: | Minor | Last Reviewed: | 7/16/2004 |
---|
Keywords: | kbBidi kbprb KB232064 |
---|
|