Search Tips

Proposed Amendments to North Dakota Rules Wednesday, August 5, 1998

IN THE SUPREME COURT

STATE OF NORTH DAKOTA

NOTICE OF HEARING

Supreme Court No. 980217

Proposed Amendments to the North Dakota Rules of Civil Procedure, Rules of Criminal Procedure, Rules of Appellate Procedure, Rules of Court and the North Dakota Century Code

The Joint Procedure Committee filed proposed amendments to Rules 4, 5, 6, 23, 30, 30.1, 31, 43, 45, 51 and 77, of the North Dakota Rules of Civil Procedure, Rules 30, 32, 32.1, 37, 45, 46, 49, and Form 8, of the North Dakota Rules of Criminal Procedure, Rules 3, 4, 8, 25, 26, 36, 42, 45, and 47.1, of the North Dakota Rules of Appellate Procedure, Rules 3.1, 6.9, 6.10, 7.1, 8.2, and 11.2, of the North Dakota Rules of Court and §27-10-01.3 of the North Dakota Century Code. A synopsis is attached. A complete copy of the proposed Amendments may be obtained from the Clerk of the Supreme Court.

ORDERED, that a hearing be held on the proposed amendments, Tuesday, October 20, 1998, at 1:30 p.m., in the Courtroom of the Supreme Court, at the State Capitol in Bismarck, North Dakota. Time for personal appearances will be limited. Any person wishing to comment on the proposed amendments may do so in writing prior to the hearing. Address written comments to Penny Miller, Clerk of the Supreme Court, 600 E. Boulevard Ave., Dept. 180, Bismarck, ND 58505-0530.

Dated: August 26, 1998.

Penny Miller
Clerk
North Dakota Supreme Court 

 

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 -->

<configuration>
    <system.web>
        <customErrors mode="Off"/>
    </system.web>
</configuration>

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 -->

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