Logo
Searching Tips

When searching Forecite California, there are shortcuts you can take to find the information you are looking for:

1. By Code Section:

Forecite uses standard abbreviations for different types of codes. Those abbreviations can be found below:

Codes:
CCR California Code of Regulations
Corp C Corporations Code
EC Evidence Code
FG Fish and Game Code
GC Government Code
HN Harbors & Navigation Code
HS Health & Safety Code
PC Penal Code
RT Revenue & Tax Code
VC Vehicle Code
WI Welfare & Institutions Code

Using these codes to search is very simple. For example, if you wanted to search for Penal Code section 20, you would type PC 20 into the search box.

2. By CALJIC Number:

Since Forecite is indexed to CALJIC, searching for CALJIC numbers is easy. For example, to search for CALJIC 3.16, you would type 3.16 into the search box.

3. By Case Name or Citation:

To find a case or citation, simply enter all or part of the case’s citation. Since many cases are known only by one name involved, it is often helpful to not search for the entire citation. For example, if you were searching for references to People v. Geiger (84) 35 C3d 510, 526 [199 CR 45], you could search for People v. Geiger or just Geiger. Searching for Geiger might be more helpful since it would find references to the case that do not include the full citation.

  • Contact Us
  • Log In
  • My Account

  • Home
  • Firm Overview
  • Attorney Profiles
  • Practice Areas
  • Verdicts & Settlements
  • News & media
  • Blog
  • Contact

Back to  Previous Page
Back to top

Server Error in ‘/’ Application.


A potentially dangerous Request.Path value was detected from the client (&).

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.Web.HttpException: A potentially dangerous Request.Path value was detected from the client (&).

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.


Stack Trace:

[HttpException (0x80004005): A potentially dangerous Request.Path value was detected from the client (&).]
   System.Web.HttpRequest.ValidateInputIfRequiredByConfig() +9672644
   System.Web.PipelineStepManager.ValidateHelper(HttpContext context) +53

 


Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.0.30319.18034

  • Register as New User
  • Contact Us
© James Publishing, Inc. (866) 72-JAMES