Visual FoxPro Programming Standards and Guidelines

Visual FoxPro Programming Standards and Guidelines Version … Visual FoxPro Development Guidelines Version 4.0 – Revised (May 16, 2004) Page 1 … LANGUAGE/VERSION: * Visual FoxPro 7.0 or … Visual FoxPro Development Guidelines Version 4.0 – Revised (May 16, 2004) Page 1 Located: K: \WLCDOCUMENTS\ADMINISTRATIVE\STANDARDS\DEVELOPERGUIDELINES4POINT0.DOC Purpose of Standards and Guidelines The definition of the word standard has many meanings, but in the context of developer standards we like the following definition: stan·dard (stan’ …
Visual FoxPro Development Guidelines Version 4.0 – Revised (May 16, 2004) Page 4 Located: K: \WLCDOCUMENTS\ADMINISTRATIVE\STANDARDS\DEVELOPERGUIDELINES4POINT0.DOC Indicator Data Type Example biv Varbinary @ l Contract img Image @ g Logo bit Bit @ l Operational tsp Timestamp @ s Current guid Uniqueidentifier @OrderId _PK/FK cur Cursor @ cur Inventory Views All local and remote view names are to use “v_” as their initial characters. The view name should include the name of the principle-underlying table used to populate the view cursor. The number of records expected in the result set should be indicated. Using the underlying table in the singular indicates that the view retrieves a single record. This will usually be used for a parameterized view using a primary surrogate or candidate natural key. Multiple-record views can be indicated by using the principle underlying table in the plural (assuming that you follow the company standard of naming tables in the singular), or by including the word “List” in the view name, e.g. v_Customers for a Customer table, v_VendorList for a Vendor table. Clause Standard Example Filter conditions can be indicated by including “For” followed by the parameterized field For v_Customers For Region v_Orders For Customer v_Employees For Department If necessary to indicate a sort order, include “By” in the view name By v_Customers By Sales v_Customers By Zip v_Customers By State v_Employees By Tenure Views that are created in code will have “ND” (for No Designer) as a suffix to the view name ND v_CustomersSales WithJoins ND Views created initially for populating combo boxes or list boxes should have “v_cbo” or “v_lst” as their initial characters cbo lst v l _CustomerList v l _EmployeesForDept Views created initially for reports should have “v_rpt” as their initial characters rpt v r _SalesYTDForCustomer v r _EmployeesByName An optional standard is to include the letters “RO” as the last two characters in the view name (or just preceding the “ND”) for views created as Read Only (non-updateable) views. In many cases, the fact that the view is not updateable can be inferred from the table name (seeing “List” in the name for example). Likewise, views that have a name identical to the underlying table (as in v_Customer for Customer) are very likely to be updateable.
Download Visual FoxPro Programming Standards and Guidelines.Pdf
sir how can I get a complete handbook about fox pro/visual foxpro?
I live in India(east regeon) & not have enough money to buy a book from market or from well known authors .
So I shall be highly obliged if you give me a solution.
REGARDS
CHIRANJIB BOSE.
DURGAPUR-18
INDIA