Search Tips

Disciplinary Board v. Bailey

Docket No. 19910148
Oral Argument: Argument Date & Time is not set.

Docket Info

Title
In the Matter of the Application
for Disciplinary Action Against
Colin A. Bailey, A Member of the
Bar of the State of North Dakota
------------
Disciplinary Board of the
Supreme Court of the State
of North Dakota, Petitioner
v.
Colin A. Bailey, Respondent
Case Type
DISCIPLINARY PROCEEDING-Lawyer : DISCIPLINARY PROCEEDINGS (Civil)
Appeal From
Case No.
472 N.W.2d 472

Highlight


Briefs

Filing Date Description

Counsel

Party Type Name
RESPONDENT PRO SE Colin A Bailey - 02837
PETITIONER DISCIPLINARY STAFF Vivian Elaine Berg - 03548

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

Seq. # Filing Date Description Attachment
1 05/16/1991 REPORT OF Disciplinary Board w/ attached Findings and
2 05/16/1991 Recommendation of Hearing Panel
3 05/16/1991 STATEMENT OF COSTS AND EXPENSES
4 05/16/1991 TRANSCRIPT DATED April 10, 1991
5 05/16/1991 Disciplinary Board documents in formal disciplinary proceed.
6 06/19/1991 Petition and Stipulation for Discipline (on 6-26-91 conf.)
7 06/26/1991 DISPOSITION
8 06/26/1991 UNANIMOUS OPINION : Per Curiam View
9 06/26/1991 S.Ct. entered Order of Public Reprimand
10 06/22/1993 Judgment for costs in the amount of $1,053.92
11 06/22/1993 JUDGMENT TRANSCRIBED TO Richland County District Court
12 06/22/1993 Affidavit of Identification
13 06/22/1993 Transcript of Judgment
14 06/30/1993 Notice of transcript
15 06/25/2001 Renewal of Judgment for $1053.92
16 06/29/2001 Notification by Richland Co. Clerk of Court that the judgement was renewed entered on 6-27-01

 


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>