^{<IRAN  SYSTEM> CODE  PAGE}

This code page had been used for many years by Farsi FoxPro programmers under DOS. Because of this capability, programmers will be easily able to convert their old DOS programs (and data, of course) that had been developed in this code page, into Windows format, by means of Pars Pendar.

^{<PANIZ> CODE  PAGE}

This code page was also of interset to some FoxPro programmers under DOS.  Because of this capability, programmers will be easily able to convert their old DOS programs (and data, of course) that had been developed in this code page, into Windows format, by means of Pars Pendar.

^{<SAYEH> CODE  PAGE}

This code page was also of interset to some FoxPro programmers under DOS.  Because of this capability, programmers will be easily able to convert their old DOS programs (and data, of course) that had been developed in this code page, into Windows format, by means of Pars Pendar.

^{<FARSI  MICROSOFT  WINDOWS> CODE  PAGE}

A very popular code page used in several types of FARSI Windows. Note that Many FARSI Windows use this code page as their default code page, and that many FARSI Visual FoxPro programmers are currently using one of such Windows.

^{<SABERIN WINDOWS> CODE  PAGE}

A very popular code page used in several types of FARSI Windows.

^{<SINA WINDOWS> CODE  PAGE}

A very popular code page used in several types of FARSI Windows.

^{CONVERTING  MILADI  DATES  TO  SHAMSI}

A very necessary capability used by most Farsi programs. This feature is completely problem free for 2000 year and later dates in addition to lower dates (i.e. there 'll be no Y2K problem when using this feature).

^{CONVERTING  SHAMSI  DATES  TO  MILADI}

Also completely problem free for 2000 year and later dates in addition to lower dates (i.e. there 'll be no Y2K problem when using this feature also).

^{EVALUATING  EITHER  SHAMSI  OR  MILADI  KABISEH  YEARS  PROPERLY}

^{CALCULATING  FARSI   MONTHS  AND  DAY  OF  WEEK}

^{TESTING  FOR  EXISTANCE  OF  A  SPECIFIED  DRIVE  IN  THE  SYSTEM}

Suppose you want to know if there is a specified drive name in the computer that is currently executing the program. There are many functions in the above library file to achieve that purpose. You can also find out the type of the specified drive (Network, Floppy, Hard, CDROM, ...). These capabilities are useful in programs that back up data.

^{FINDING  OUT  IF  THE  DISK  IN  A  DRIVE  IS  WRITE  ENABLED}

Also useful in programs that back up data or want to save data on a disk. There's a function that shows if a disk in a specified drive is write protected.

^{FINDING  OUT  IF  THERE  IS  A  DISK  IN  A  DRIVE  (IS  A  DRIVE  READY ?)}

Useful in programs that read data from a disk.

^{CREATING  AND  REMOVING  FOLDERS.}

UsefulNESS OF SUCH FUNCTIONS in programs are obvious.
 

^{FIXING  THE  FLAG  OF  CDX  FILES  IN  DBF  FILES}

Useful in ON ERROR ... routins in your programs, where you might need to repair the damaged or corrupted DBF files. You can also use it outside error capturing routines.

^{EXTRACTING  FILE  SIZES  (ANY  KIND  OF  FILES)}

^{EXTRACTING  CHECKSUMS  FOR  ANY  KIND  OF  FILES}

^{FAST  AND  PRECISE   FILE  ENCRYPTION  (BY  2  METHODS  :  ELEMENTARY  &  ADVANCED)}

^{FAST  AND  PRECISE   FILE  DECRYPTION  (BY  2  METHODS  :  ELEMENTARY  &  ADVANCED)}
 

^{NOTE :}

Pars Pendar does not conflict with Visual FoxPro's intrinsic & built in capabilities while in a left to right Farsi/Latin data entry mode at runtime. In other words, Pars Pendar supports ALL NATURAL VFP'S CAPABILITIES in data entry sessions, such as : ON KEY LABEL, CUT, COPY, PASTE, ANY MOUSE ACTIVITY, etc.

Environments in which end users can enter left to right Farsi/Latin data at program runtime, include : @ ... GET ... command, BROWSE, TEXT BOX CONTROLS (in Form Designer), and finally, GRID CONTROLS (in Form Designer).

^{3  BY  3  DIGITS  SEPARATION  OF  FARSI / LATIN  NUMERICS}

^{NUMBER  TO  CHARACTER  CONVERSION  (APPROPRIATE  FOR  FARSI  SPELLING)}

^{CONVERTING  NATURAL  NUMERICS  TO  THEIR  FARSI  EQUIVALENTS  (AND  VICE  VERSA)}

^{NOTE :}

Pars Pendar does not conflict with Visual FoxPro's intrinsic & built in capabilities while in a right to left Farsi/Latin data entry mode at runtime. In other words, Pars Pendar fully supports ALL NATURAL VFP'S CAPABILITIES in data entry sessions, such as : ON KEY LABEL, CUT, COPY, PASTE, ANY MOUSE ACTIVITY, etc.

Environments in which end users can enter right to left Farsi/Latin data at program runtime, include : @ ... GET ... command, BROWSE, TEXT BOX CONTROLS (in Form Designer), and finally, GRID CONTROLS (in Form Designer).
 

^{NOTE  1 :}

Word wrapping is maintained automatically. Environments in which end users can enter right to left multi line text (Farsi/Latin) at program runtime, include : @ ... EDIT ... command and EDIT BOX CONTROLS (in Form Designer).

^{NOTE  2 :}

Pars Pendar's related capabilities are not limited to just what we mentioned above. Pars Pendar, in fact, gives you more flexible functions while working with multi line text boxes. Please refer to other parts of the documentation presented in our web site. You can simply visit our General information page for more details regarding Pars Pendar's features.

^{NOTE  3 :}

Pars Pendar assigns a 20KB memory buffer for manipulation of the data while working with SMEMOLIB.FLL. In fact, end users won't be able to type characters more than 20 kilo bytes in that case. For larger memory buffers, you must use LMEMOLIB.FLL or XMEMEOLIB.FLL.
 

^{NOTE  1 :}

Word wrapping is maintained automatically. Environments in which end users can enter right to left multi line text (Farsi/Latin) at program runtime, include : @ ... EDIT ... command and EDIT BOX CONTROLS (in Form Designer).

^{NOTE  2 :}

Pars Pendar's related capabilities are not limited to just what we mentioned above. Pars Pendar, in fact, gives you more flexible functions while working with multi line text boxes. Please refer to other parts of the documentation presented in our web site. You can simply visit our General information page for more details regarding Pars Pendar's features.

^{NOTE  3 :}

Pars Pendar assigns a 64KB memory buffer for manipulation of the data while working with LMEMOLIB.FLL. In fact, end users won't be able to type characters more than 64 kilo bytes in that case. For larger memory buffers, you must use XMEMOLIB.FLL.

^{NOTE  1 :}

Word wrapping is maintained automatically. Environments in which end users can enter right to left multi line text ( Farsi/Latin) at program runtime, include : @ ... EDIT ... command and EDIT BOX CONTROLS (in Form Designer).

^{NOTE  2 :}

Pars Pendar's capabilities is not limited to just what we mentioned above. Pars Pendar, in fact, gives you more flexible functions while working with multi line text boxes. Please refer to other parts of the documentation presented in our web site. You can simply visit our General information page for more details regarding Pars Pendar's features.

^{NOTE  3 :}

Pars Pendar assigns a 128KB memory buffer for manipulation of the data while working with XMEMOLIB.FLL. In fact, end users won't be able to type characters more than 128 kilo bytes in that case.

^{NOTE :}

The above library works in three distinct modes (selectable by the programmer) as follows : (in either modes, the table must have been indexed on a key field in advanced).

^{IMMEDIATE  MODE}

In this mode, searching starts immediately after each keystroke. This may be time-consuming when dealing with large tables.

^{DELAYED  MODE}

In this mode, searching starts only after hitting the <ENTER> key, which in turn, usually occurs after all the desired characters have been typed on the keyboard.

^{USER  DEFINED  (ARBITRARY)  MODE}

In this mode, Pars Pendar will never start searching automatically for the records that match keystrokes. In fact, programmer must themselves define an ON KEY LABEL routine (or the like) of their own, in which the action of each keystroke has been defined upon a user defined manner.

^{NOTE :}

Pars Pendar's capabilities is not limited to just what we mentioned above. Pars Pendar, in fact, gives you more flexible functions while working with SEEKLIB.FLL. Please refer to other parts of the documentation presented in our web site. You can simply visit our General information page for more details regarding Pars Pendar's features.
 

^{CONVERTING  LOWERCASE  FARSI  STRINGS  TO  UPPERCASE}

^{CONVERTING  UPPERCASE  FARSI  STRINGS  TO  LOWERCASE}

^{FINDING  OUT  IF  THE  LEFTMOST  CHARACTER  IN A  FARSI  STRING  IS  A  LOWERCASE  ONE}

^{FINDING  OUT  IF  THE  LEFTMOST  CHARACTER  IN A  FARSI  STRING  IS  A  UPPERCASE  ONE}

^{CONVERTING  THE  LAST  CHARACTER  IN  A  FARSI  STRING  TO  UPPERCASE}

^{DELETING  (TRIMMING)  ALL  SPACES  IN  A  STRING}

^{DELETING  (TRIMMING)  ALL  SKETCHING  CHARACTERS  (KESHIDEGI)   IN  A  STRING}