U.S. Federal and State Cases, Codes, and Articles
Select a tab to search United States Cases, Codes, or Articles
U.S. Federal and State Cases, Codes, and Articles
Select a tab to search United States Cases, Codes, or Articles
Search for cases
Indicates required field
Search by keyword or citation
Indicates required field
Search blogs, article pages, and cases and codes
Indicates required field
Current as of January 01, 2024 | Updated by FindLaw Staff
The state is not liable for a claim arising upon contract which is the result of the failure of any computer hardware or software, telecommunications network, or device containing a computer processor to interpret, produce, calculate, generate, or account for a date that is compatible with the year 2000 date change if the state has made a good-faith effort to make the computer hardware or software, telecommunications network, or device containing a computer processor compliant with the year 2000 date change. For the purposes of this section, the state is presumed to have made a good-faith effort to make the computer hardware or software, telecommunications network, or device containing a computer processor compliant with the year 2000 date change if the results of testing establish that the computer hardware or software, telecommunications network, or device containing a computer processor meets the compliance requirements of this section, or if the state has sought and received an assurance of compliance from the manufacturer or supplier, or if the state has sought an assurance of compliance from the manufacturer, supplier, government, or other reliable source when testing or receiving an assurance from the manufacturer or supplier of the computer hardware or software, telecommunications network, or device containing a computer processor is not practicable. For the purposes of this section, computer hardware or software, a telecommunications network, or device containing a computer processor is compliant with the year 2000 date change if:
1. All stored dates or programs contain century recognition, including dates stored in databases and hardware or internal system dates in devices;
2. The program logic accommodates same century and multicentury formulas and date values; and
3. The year 2000 or any other leap year is correctly treated as a leap year within all program logic.
Cite this article: FindLaw.com - North Dakota Century Code Title 32. Judicial Remedies § 32-12-05. Claims resulting from year 2000 date change computer failures prohibited - last updated January 01, 2024 | https://codes.findlaw.com/nd/title-32-judicial-remedies/nd-cent-code-sect-32-12-05/
FindLaw Codes may not reflect the most recent version of the law in your jurisdiction. Please verify the status of the code you are researching with the state legislature or via Westlaw before relying on it for your legal needs.
A free source of state and federal court opinions, state laws, and the United States Code. For more information about the legal concepts addressed by these cases and statutes, visit FindLaw's Learn About the Law.
Get help with your legal needs
FindLaw’s Learn About the Law features thousands of informational articles to help you understand your options. And if you’re ready to hire an attorney, find one in your area who can help.
Search our directory by legal issue
Enter information in one or both fields (Required)