📄 business.html

📁 its it tracker and used for track
💻 HTML
字号:
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" >
<head>
    <title>ITracker Help</title>
</head>
<body>
    <p style="text-align:center;width:500px;"><span style="font-size:20pt;font-weight:bold;">ITracker Business Help</span><br />
        <a href="default.html">Help Home</a> | <a href="site.html">Site/Page Help</a> | <a href="business.html">Business Help</a> | <a href="database.html">Database Help</a>
    </p>
    <p style="text-align:center;width:500px;">
    The Business Layer portion of the application is quite simple. It consists of 2basic files with each of the files
    consisting of 2 classes. A simple object class and a collections class. Since both of these files follow the same 
    methodology I will only go into details on one of them (being the Vendor.vb file).
    </p>
    <p style="width:500px;">
    <b>Vendor.vb</b> consists of two basic classes, Vendor and VendorList. Here is a diagram detailing out the 
    classes.<br />
    <img onclick="window.open('../images/ITrackerBusinessDiagram.jpg');" src="../images/ITrackerBusinessDiagram.jpg" alt="Click for full sized diagram" width="495px" style="cursor:hand;" />
    <br />
    <b>VendorList</b>, as you can see, is really nothing more then a collection object. It only serves as a way to hold
    multiple vendors together at once. For that reason I won't really go into much detail on it but I'm sure that 
    there is really little need to.<br />
    <b>Vendor</b> is the real heart of the file. This class has all the individual properties as well as all the methods/functions
    needed to work with this object. While I've only done some basics I'm sure you can see how you could easily extend the class to
    incorporate validations, default values, etc. The core functions for the class are the Fetch/FetchList, Save, Search and ConvertToObject.
    I always try to name my functions as such so that you can easily know what it is that they do. The Fetch/FetchList are simple functions 
    that call out to the Data Access Layer to gather 1 or more items. The Search function acts in a very similar way to the Fetch calls
    with the only difference being that there are unknown paramaters, or rather unknown if they are used/populated. The Search & Fetch calls
    both get a returning DataSet from the Data Access Layer and pass it to the ConvertToOject function. This function is really only
    there to appropriately place the data into the right property in the object. The last function is the Save function. Again, as the name
    implies the function is designed to simply pass the object (or in this case the object properties) to the underlying Data Access
    Layer and return a pass/fail indicator. This is another area that could easily be extended to allow the user to pass back things 
    like the new ID or even a string containing a more detailed error message should one arise.
    </p>
    <p style="width:500px;">
        These files, and the classes contained within, are meant to be starting points. They are fully workable but again, like
        most of the application they are only meant to get you going. You will definitley want to extend these classes to
        fit your own needs. Items like validations and more properties (phone number perhaps?) would all be great things to play
        around with to get you going.
    </p>
    <p style="text-align:center;width:500px;">
        ~
        <br />
        Curt Christianson<br />
        <a href="mailto:darkfalz@darkfalz.com">darkfalz@darkfalz.com</a><br />
        www.Darkfalz.com<br />
        www.DF-Software.com<br />
        
    </p>
</body>
</html>
⌨️ 快捷键说明

复制代码 Ctrl + C
搜索代码 Ctrl + F
全屏模式 F11
切换主题 Ctrl + Shift + D
显示快捷键 ?
增大字号 Ctrl + =
减小字号 Ctrl + -