Search Tips

Amendments to NDRCivP, NDRCrimP, NDREv, NDRAppP, NDRCt, etc.

Docket No. 19990237
Oral Argument: Tuesday, October 26, 1999 2:45pm

Docket Info

Amendments to the North Dakota Rules of Civil
Procedure, Criminal Procedure, Evidence,
Appellate Procedure, North Dakota Rules of Court,
North Dakota Supreme Court Administrative Rules,
and North Dakota Rule on Local Court Rules
Case Type

(Note: Attachments may not be available for recently filed cases and/or confidential documents.)

Seq. # Filing Date Description Attachment
1 08/02/1999 PETITION FILED by Joint Procedure Committee w/attached proposed amendments View
2 08/12/1999 Notice of Hearing mailed to Joint Procedure Committee, Clerk's Office Misc., Judges (dt/fed/surr);
3 08/12/1999 Clerks, SBAND, NDTLA
4 10/06/1999 Letter from Vince H. Ficek dated 10-5-99 RE: Rule 407,NDROE (Distributed to Justices & Gary R.) View
5 10/08/1999 Letter from Rebecca S. Thiem dated October 6, 1999, on behalf of the the Bar Board RE: Rule 11.1 View
6 10/26/1999 APPEARANCES: Gerhard F. Raedeke, Rebecca S. Thiem
7 10/26/1999 ARGUED: Raedeke; Thiem (Vol. W; page 191)
8 11/17/1999 DISPOSITION (effective March 1, 2000) View
9 11/17/1999 ACTION BY SUPREME COURT (petition granted) - Granted
10 11/23/1999 Order of Adoption with Rules attached Mailed to Joint Procedure Committee, Judges(district/fed/
11 11/23/1999 surrogate), Clerks, Clerk's office misc., NDTLA, SBAND
12 03/13/2007 EXPUNGED - Nonpermanent record items destroyed


Runtime Error

Server Error in '/' Application.

Runtime Error

Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.

Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".

<!-- Web.Config Configuration File -->

        <customErrors mode="Off"/>

Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL.

<!-- Web.Config Configuration File -->

        <customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/>