Laserfiche WebLink
<br />Water Information <br />Sheet data <br />management <br /> <br />Diversions <br /> <br />Exehanges <br /> <br />Dusly existing overlay for this Water Information Sheet is erased, and the sheet is <br />saved using the DMI functions erase_old_wis (), SQLlnsertWis- <br />Header (), SQLlnsertWisRow (), SaveDiversionList () , and <br />SaveExchangeLi s t () specifying the use of the Overlay tables. <br /> <br />The function LoadlnfoSheetForOverlay () is used to create an nearly <br />empty Water Information Sheet suitable for overlay generation (by LoadOver- <br />layFiIe ()). The information sheet is created using the DMI commands <br />CreateWISHeader () and CreatelnfoSheet () and initialized only with <br />existing overlay information (loaded with a calI to LoadOverlay ( )). <br /> <br />Water Information Sheet data is managed with the structures outlined above, the <br />"Water Information Sheet" section on page] 9. Data from the <br />info_sheet_header_rec struct is stored in a separate database table called <br />wis_comments. This table holds the comment at the bottom of the sheet, the date of <br />the sheet, and the date/time the sheet was last saved. Data from the rows and columns <br />of the Water Information Sheet are saved in the table wis_data. Any data which is <br />derived from stored data (e.g., formula rows and total diversions) are not saved in the <br />database. Instead, these data are derived from the stored data every time the sheet is <br />loaded. <br /> <br />The Water Information Sheet is the source of all diversion and exchange data that <br />enters SPWRMS. These data are associated with structures in a many-to-one relation- <br />ship-any number of diversions or exchanges may be diverted through a structure. <br />For this reason, separate data structures and database tables are required to manage <br />the data. <br /> <br />Overlay tables identical to the Water Information Sheet tables are also available in the <br />database. All of the load and save routines for the water information sheets are <br />parameterized to control which set of tables (official or overlay) to read from and save <br />to. <br /> <br />A linked list of di version_recs is attached to each row of type struct in the <br />Water Information Sheet. This list holds all the priority diversions at that structure. <br />These diversions are stored in the database table diversions. <br /> <br />The DMI routine LoadDiversionList () is used to create this list. <br /> <br />A linked list of exchange_recs is attached to each row of type struct in the Water <br />Information Sheet. This list holds all the priority diversions at that structure. These <br />exchanges are stored in the database table exchanges. <br /> <br />The DMI routine LoadExhangeList () is used to create this list. <br /> <br />Call Management <br /> <br />Call manipulations (setting or releasing calls) require reestablishing the application's <br />representation of the call structure. Calls can be set and released by other users of the <br />system, so whenever the user asks to view call information, the application verifies <br />that its representation is up-to-date. See the "Synchronizing with the database" <br />section on page 15 for details of this verification process. <br /> <br />34 <br />