Legal Opinion

Currie v. Stewart

Mississippi Supreme Court

Decided April 15, 1854PublishedCited by 5 opinions

In error from the circuit court of Hinds county; Hon. R. Barnett, judge. William C. Currie, as administrator of the estate of Abraham Whitaker, deceased, sued upon a writing obligatory executed by William B. Stewart et al., for the purchase-money of a tract of land sold by Currie, administrator, &c.,' under an order of the probate court of Hinds county.

Read the full summary

In error from the circuit court of Hinds county; Hon. R. Barnett, judge. William C. Currie, as administrator of the estate of Abraham Whitaker, deceased, sued upon a writing obligatory executed by William B. Stewart et al., for the purchase-money of a tract of land sold by Currie, administrator, &c.,' under an order of the probate court of Hinds county. The defence set up by Stewart et al. to the note was, that the sale of the land by the administrator was made without any legal authority, the proceedings and order of sale in the probate court being irregular and void. Whitaker, the deceased,…

1Opinion of the CourtJustice Handy

The plaintiff in error brought this action against the defendants upon a writing obligatory executed by them to him for the purchase-money of a tract of land sold by the plaintiff under an order of the probate court of Hinds county. The defence in the court below was, in substance, that the sale was made without rightful authority, the proceedings and order of sale in the probate court being irregular and void. The material facts necessary to be noticed appear in the petition and proceedings in the probate court. The petition is in the name of the plaintiff, as administrator of Abraham…

2Cited by5 opinions

  1. Haynes v. MeeksCalifornia Supreme Court · 1862
  2. Root v. McFerrinMississippi Supreme Court · 1859
  3. Mumper v. MatthesOregon Supreme Court · 1949
  4. Clay v. FieldSupreme Court of the United States · 1885
  5. Kempe v. PintardMississippi Supreme Court · 1856

Showing a preview — retrieve the full document via the Exa API.

Powered by the Exa API