The WinBuilder database management system (DBMS) project is predicated on two suppositions:
The first supposition takes note of the fact that Microsoft recognized the severe limitations of flat-file (.INI) based systems management some considerable time ago. In addition to their inherent file size limits, INI files place insurmountable restrictions on the types of data it is possible to record and handle. Perhaps most important from the developer perspective, however, is the nuisance factor involved in their individual local maintenance – as if the documentation of scripts themselves wasn't sufficient overburden for creative people with much better activities to occupy their time.
The second aspect presumes that, sooner or later, if not immediately, the complexities of "shopping" for compatible "bits and pieces" to fulfill individual requirements under a multiplicity of APIs and related component issues is bound to overwhelm the end user, if not the system itself. The local maintenance of flat-file records is simply not up to the challenge that ultimately faces both ends of an increasingly diverse system and its very wide-spectrum community of users.
A relational DBMS appears to provide the obvious solution to both of these concerns, excepting only
that the concept itself tends to be somewhat frightening for those who, quite understandably, assume
that its complexities will be reflected in ways that are less "user friendly" than what has come to
be regarded as an "old friend" and familiar methodology. A primary objective of this project is to
clearly demonstrate the exact opposite: the more sophisticated the underlying technology, the greater
its capability for offering a friendly and convenient tool to ALL of its clients and users.
The WinBuilder database management system is a multi-faceted project that aims to offer a variety of interfaces depending on the nature and needs of those who interact with it. The remainder of this document will reflect that fact by providing information that is similarly categorized under sub-headings that will be of particular interest to some and of no interest whatever to others. The following features are highlights only.
Nothing could be simpler. You will see exactly the same thing regardless of which WinBuilder DBMS site you visit, regardless of whether it's the main DBMS host (currently residing at http://virtech.org/winbuilder/) or any client domain site (demo at http://browser.winbuilder.net/). Just chose your option to search, browse or list a complete WinBuilder project.
Sorry, but you will need to fill out a brief form and press a button to register your site as a client domain. To get started, go to http://virtech.org/winbuilder/wbnewreg.php and complete the form entries there.
The form itself explains each of its entry fields. (Just hover your mouse over the field label.) When completed, there is a brief on-site verification process just to ensure that you didn't miss something completely. It can't actually check the accuracy of what you do enter, of course, but most things can be modified later when you log in. Press the "Add New" button and a customized client package will then be prepared just for you to download.
Install the downloaded client package in any (sub)folder on your site that has direct HTTP and FTP access to the absolute paths that you entered in the registration form. (That's a security feature for your protection, not a program limitation, BTW.) And that's the complete set-up. You're done.
You can now log in as the primary administrator of your own WinBuilder DBMS domain and add or change whatever suits your preferences, including the addition of others with full or partial admin privileges if you wish. Explore. Have fun. You can post any questions in the Boot-Land forum or my own.
Know something? I'm tired of typing. I already said there's a fully automated set-up. I'll write the rest if and when it's actually needed – if ever.