To perform an arithmetic on a file time, you need to convert the FILETIME to a quadword (a 64-bit integer), perform the arithmetic, and then convert the result back to a FILETIME. Assuming ft is a FILETIME structure containing the creation time of a file, the following sample code adds 30 days to the time. A function using the FILETIME structure can allow for values outside of zero or positive values typically specified by the dwLowDateTime and dwHighDateTime members. For example, the SetFileTime function uses 0xFFFFFFFF to specify that a file's previous access time should be preserved. Represents file time. Trivial-clock is an implementation-defined type that satisfies TrivialClock and is sufficient to represent the resolution and range of the file time values offered by the filesystem. FILETIME: 100-nanoseconds since Jan 1 1601: 6000004:8BC25000. FileTime saves your file marked, in and outbound service documents and outbound faxed document(s) for up to 3 years. Date and time is recorded for your convenience. Extended File Stamped Service Document Storage FileTime saves a file stamped copy of any eService documents served to you by counsel.

• Class

Class FileTime

• • java.nio.file.attribute.FileTime

• All Implemented Interfaces:

  Comparable<FileTime>

  
  
  Represents the value of a file's time stamp attribute. For example, it may represent the time that the file was last modified, accessed, or created.

  Instances of this class are immutable.

  Since:

  1.7

  See Also:

  Files.setLastModifiedTime(java.nio.file.Path, java.nio.file.attribute.FileTime), Files.getLastModifiedTime(java.nio.file.Path, java.nio.file.LinkOption...)

• • Method Summary

    Methods

    Modifier and Type	Method and Description
    int	compareTo(FileTime other) Compares the value of two FileTime objects for order.
    boolean	equals(Object obj) Tests this FileTime for equality with the given object.
    static FileTime	from(long value, TimeUnit unit) Returns a FileTime representing a value at the given unit of granularity.
    static FileTime	fromMillis(long value) Returns a FileTime representing the given value in milliseconds.
    int	hashCode()
    long	to(TimeUnit unit) Returns the value at the given unit of granularity.
    long	toMillis()
    String	toString() Returns the string representation of this FileTime.

    • Methods inherited from class java.lang.Object

      clone, finalize, getClass, notify, notifyAll, wait, wait, wait

• • Method Detail

    • from

      Returns a FileTime representing a value at the given unit of granularity.

      Parameters:

      value - the value since the epoch (1970-01-01T00:00:00Z); can be negative

      unit - the unit of granularity to interpret the value

      Returns:

      a FileTime representing the given value

    • fromMillis

      Returns a FileTime representing the given value in milliseconds.

      Parameters:

      value - the value, in milliseconds, since the epoch (1970-01-01T00:00:00Z); can be negative

      Returns:

      a FileTime representing the given value

    • to

      Returns the value at the given unit of granularity.

      Conversion from a coarser granularity that would numerically overflow saturate to Long.MIN_VALUE if negative or Long.MAX_VALUE if positive.

      Parameters:

      unit - the unit of granularity for the return value

      Returns:

      value in the given unit of granularity, since the epoch since the epoch (1970-01-01T00:00:00Z); can be negative

    • toMillis

      Returns the value in milliseconds.

      Conversion from a coarser granularity that would numerically overflow saturate to Long.MIN_VALUE if negative or Long.MAX_VALUE if positive.

      Returns:

      the value in milliseconds, since the epoch (1970-01-01T00:00:00Z)

    • equals

      Tests this FileTime for equality with the given object.

      The result is true if and only if the argument is not null and is a FileTime that represents the same time. This method satisfies the general contract of the Object.equals method.

      Overrides:

      equals in class Object

      Parameters:

      obj - the object to compare with

      Returns:

      true if, and only if, the given object is a FileTime that represents the same time

      See Also:

      Object.hashCode(), HashMap

    • hashCode

      Computes a hash code for this file time.

      The hash code is based upon the value represented, and satisfies the general contract of the Object.hashCode() method.

      Overrides:

      hashCode in class Object

      Returns:

      the hash-code value

      See Also:

      Object.equals(java.lang.Object), System.identityHashCode(java.lang.Object)

    • compareTo

      Compares the value of two FileTime objects for order.

      Specified by:

      compareTo in interface Comparable<FileTime>

      Parameters:

      other - the other FileTime to be compared

      Returns:

      0 if this FileTime is equal to other, a value less than 0 if this FileTime represents a time that is before other, and a value greater than 0 if this FileTime represents a time that is after other

    • toString

      Returns the string representation of this FileTime. The string is returned in the ISO 8601 format: where '[.s+]' represents a dot followed by one of more digits for the decimal fraction of a second. It is only present when the decimal fraction of a second is not zero. For example, FileTime.fromMillis(1234567890000L).toString() yields '2009-02-13T23:31:30Z', and FileTime.fromMillis(1234567890123L).toString() yields '2009-02-13T23:31:30.123Z'.

      A FileTime is primarily intended to represent the value of a file's time stamp. Where used to represent extreme values, where the year is less than '0001' or greater than '9999' then this method deviates from ISO 8601 in the same manner as the XML Schema language. That is, the year may be expanded to more than four digits and may be negative-signed. If more than four digits then leading zeros are not present. The year before '0001' is '-0001'.

      Overrides:

      toString in class Object

      Returns:

      the string representation of this file time

• Class

• Summary:
• Nested |
• Field |
• Constr |

• Detail:
• Field |
• Constr |

Submit a bug or feature
For further API reference and developer documentation, see Java SE Documentation. That documentation contains more detailed, developer-targeted descriptions, with conceptual overviews, definitions of terms, workarounds, and working code examples.
Copyright © 1993, 2020, Oracle and/or its affiliates. All rights reserved. Use is subject to license terms. Also see the documentation redistribution policy.

Scripting on this page tracks web page traffic, but does not change the content in any way.

eFiling to the court can be a daunting task, that’s why at FileTime we spent years working with attorneys, firm administrators and firm support teams to provide the best possible system to make eFiling simple and straightforward.

File Time Ca

1. Know your Deadline

If you want to guarantee that you meet the eFiling deadlines that are approaching, you may want to make yourself aware of the eFiling rules.

A document is considered timely filed if it is electronically filed at any time before midnight (in the court's time zone) on the filing deadline. An electronically filed document is deemed filed when transmitted to the filing party's electronic filing service provider, except:

File Timer

• If a document is transmitted on a Saturday, Sunday, or legal holiday, it is deemed filed on the next day that is not a Saturday, Sunday, or legal holiday; and,
• If a document requires a motion and an order allowing its filing. it is deemed filed on the date the motion is granted

Be aware of returned for correction documents as you may only have up to 24 hours to complete the corrections to be made to qualify for keeping the original submission date/time. We urge you to plan ahead when it comes to eFiling.

2. Plan ahead

Expect the unexpected. Although, FileTime has 96% reliability rate, we all know that technology has its good and bad days. If the eFiling Manager has a technical problem, it can affect all eFiling Service Providers.

At FileTime, we do not want you to miss any deadlines; therefore, try to plan to file 3 days before your deadline to avoid any technical errors. If a document is untimely due to a technical failure, the party may seek appropriate relief from the court. If the missed deadline is one imposed by these rules, the filing party must be given a reasonable extension of time to complete the filing.

Tip for payments: If you are using a prepaid or debit card, it would be wise to take into consideration that a returned or cancelled filing will take out the preauthorization fee and will not return it for 3-10 business days. This may put a hold on your submission date.

3. Submit the right document

Documents are usually the main reason for an issue with the filing. Here are some pointers that you should consider before pressing submit:

• The eFiling System requires all documents to be in a text-searchable PDF format in order for the clerk to receive them.
• Internal links, which point to other places within the same document are permissible. However, external links, which point to other documents, websites, or other legal sources, must be avoided in documents submitted to the court. Use of external links will cause eFileManager to reject the filing containing the document with external links.
• Clerk Requirements- Each clerk has their own requirements; therefore, we gathered all the information for this type of situation. Find your jurisdiction’s policies on our knowledge base.
• Don’t forget to sign the document! You do not need to physically sign your eFile document(s). The rules of procedure specify that /s/ [yourname] constitutes your electronic signature on the eFiled document.

If your document is not a PDF, text-searchable or 8.5x11 inches then just log into FileTime, upload your word processor file so we can convert your document into the correct format and standards that is required to eFile!

Tip to remember: The eFiling System allows the Clerks’ offices to make minor changes to filings. You may see a difference between the fees for the submission you submitted versus the final acceptance fees. In most cases, clerks’ office will return the filing for the filer to make the corrections.

4. Scan your document correctly

• Make sure your scanner is set to create documents that are 8.5” wide by 11” high. The clerk can strike documents that are larger or smaller or turned sideways.
• Make sure that your scanner is set to create black and white images, not color.
• Set the dpi (dots per inch) at 300.

Any documents filed with color images must have a minimum resolution of 600 dpi. The system will accept color documents. However, the preferred business process is to scan the documents in black and white.

File Time Converter

Pay attention to the size of the documents. The maximum total file size for all documents is 35mb. If your document exceeds the 35mb, try to reduce the dpi setting on your scanner. However, scanned PDF files are larger than those directly converted from word processor files to PDF files. You can upload your document to FileTime and we can convert it to a PDF for you to ensure you stay under 35mb.

5. Ask for help and Take a Break

Taking breaks frequently during the workday will allow you to re-energize and focus on the task in hand.

File Time Login

Our Customer Support Team are available via Phone Chat and Email. We can assure that all the information you need to file is available. Let us help you!

Press Contact
Bud Panjwani
FileTime
bud@filetime.com
1-800-658-1233 ext 11