Converting SIR 3.2 Databases to SIR2002 A Practical Guide to Coming of Age in SIR Land © Tom Shriver, DataVisor 2002

Converting SIR 3.2 Databases to SIR2002 A Practical Guide to Coming of Age in SIR Land © Tom Shriver, DataVisor 2002

Moving from SIR 3.2 to SIR2002 © 2002 Tom Shriver, DataVisor3 The Big Leap SIR 3.2 to SIR2002 u Differences for End-Users n "Windowy" Front End for SIR and Applications n Learning Curve and Anxiety Much Reduced u Differences for Programmers n All the old stuff works n A whole new GUI world to learn (Visual PQL) n Several Screen Painters Available u Differences for DBAs and DB Designers n Alternate Indexes n Multiple Databases n More Flexible Control of Master n ODBC and HTML Support

Moving from SIR 3.2 to SIR2002 © 2002 Tom Shriver, DataVisor4 How to Technicalities Initial Conversion 1. Export from "Old" SIR version 2. Import Using SIR2002 u Unload / Reload Doesn't work this Time n Variable length Strings n Max Update Level Changed (32,756 to 2.2 billion) u Recompile n Stored Executables n Forms n Subroutines

Moving from SIR 3.2 to SIR2002 © 2002 Tom Shriver, DataVisor5 Changes with Interactive SIR Initialization u Don't have to be connected to a database  Default "Profile Member" is SYSTEM.START If it doesn't exist, SYSPROC.SYSTEM.START May still specify " EX= " on execution statement u Interactive SIR is a "Menu Window" Either a Local Menu is Started by EX member, or n SIR will start one for you

Moving from SIR 3.2 to SIR2002 © 2002 Tom Shriver, DataVisor6 Converting 3.2 "User Menus" to SIR2002 u Possible to Convert with a Program n Ask David Baxter or see me u Recommendation: So many things have changed, start over 1. Pick out Menu Options you want to Preserve 2. Note what they do (probably CALL a member) 3. Pay attention to the next presentation on "Menus in SIR2002"

Moving from SIR 3.2 to SIR2002 © 2002 Tom Shriver, DataVisor7 PQL to VisualPQL: Character Graphics to Graphical User Interface u Ver 3.2 Graphical Applications n 25 x 80 Screen n Display and Operation reasonably separate n Could Preserve Display across routines u Ver 3.2 Graphical Programs in SIR200+ n Work in SIR2002 in "Execution Window" n Don't Look as Nice n Loose some Key Mapping detail u SIR2000 & SIR2002 Graphical User Interface n Graphical Objects more complex n Most Objects bound to a "Dialog" or "Window"

Moving from SIR 3.2 to SIR2002 © 2002 Tom Shriver, DataVisor8 Converting 3.2 Graphical PQL to VisualPQL u Conversion takes some thought and work n Look and Feel n Hotkey Driven vs. Mouse Driven Interface n Visual PQL has Dialogs oUnits with related Screen Objects (Controls) o"Pop-Up" standard dialogs that are very handy Example: Converting Vertical Menu to PQL Dialog -- on DataVisor CD GUIMENU.PQL a parameterized CALL procedure

Moving from SIR 3.2 to SIR2002 © 2002 Tom Shriver, DataVisor9 Converting FORMS u SIR/Forms still works in SIR2002 as Separate Module n Recompile old definitions n It is relatively easy to start Form from DBMS (with Escape) u PQL Forms is intended to be Painted, not Programmed n Bad News: Probably have to start from scratch n Good News: All your design work is done u Internal PQL Forms Command Syntax is Similar, not Identical to 3.2 Forms Syntax n Cannot Cut & Paste v3.2 Forms code into PQL Form

Moving from SIR 3.2 to SIR2002 © 2002 Tom Shriver, DataVisor10 DataBase Design Considerations u Many New Features offer Food for Thought n Rectypes for Inverted Lists Replaced by Alternate Indexes n Tabfiles for LookUp Tables Replaced by Multiple Database Processing n Long Strings may change some approaches

Moving from SIR 3.2 to SIR2002 © 2002 Tom Shriver, DataVisor11 Application Design Considerations u Integrated Visual PQL Offers Flexibility u Menu System Control u Several Screen Painters available n Data Entry Screens n For Locally Defined Utilities