Frick v. Barbour
Supreme Court of Pennsylvania
Error to the Court of Common Pleas of Montgomery county: No. 97, to July Term 1868. The action in the court below was assumpsit, by James L. Barbour and others, partners, &c., against Jacob Erick, Ephraim B. Erick and Amos Erick, partners, trading as Jacob Erick. It was commenced October 31st 1867. E. B. Erick filed an affidavit denying the partnership. The defendants pleaded non assumpsit with leave to give the special matters in evidence.
Read the full summary
Error to the Court of Common Pleas of Montgomery county: No. 97, to July Term 1868. The action in the court below was assumpsit, by James L. Barbour and others, partners, &c., against Jacob Erick, Ephraim B. Erick and Amos Erick, partners, trading as Jacob Erick. It was commenced October 31st 1867. E. B. Erick filed an affidavit denying the partnership. The defendants pleaded non assumpsit with leave to give the special matters in evidence. The ease was tried May 27th 1868, before Chapman, P. J. Eor plaintiffs: J. L. Hahn testified, he was a partner with Jacob Erick from August 14th 1861 till…
1Opinion of the Court
The opinion of the court was delivered,
by Thompson, C. J.
— We see not wherein the books of Hahn & Frick were not evidence on the question of the partnership between the Fricks. Hahn testified to the books, and to facts and declarations tending to show that Ephraim and Amos were partners with Jacob and him. This testimony, whether very important or of little consequence in the minds of the jury, could not have been withheld from them, fo.r anything we can see. Indeed it may have been very important. There was no error in its admission.
There was nothing wrong in the pertinent inquiry of the…
2Cited by9 opinions
- Hall v. VanderpoolSupreme Court of Pennsylvania · 1893
- McHugh v. McHughSupreme Court of Pennsylvania · 1898
- Cobb v. MartinSupreme Court of Oklahoma · 1912
- Wills v. HardcastleSuperior Court of Pennsylvania · 1902
- Steel v. SnyderSupreme Court of Pennsylvania · 1928
4 more not listed; retrieve them via the Exa API.