OOOForum posts and associated databases
What follows is just a description of items on my machine. The screenshots are of forms that I created as examples for people on the OOOForum. The database files they use are my own creation as are any associated basic libraries.
One good thing about this motly group is this. Almost always when building these examples I used tables created with the Base wizard. I had hoped that this would allow me at some point to re-use much of the work done on the forms (Reports), queries and or macros. In reviewing the files, it appears that this will be the case.
A second thing is that each form, or groups of forms, or basic procedures actually implements most of the functionality for some business function. Keep in mind these where all written as examples, not work for hire, so lots of the bells and whistles are missing. Error handling for one, there isn't much. But even so, there is a lot to be used as a leg up for this project.
As for the basic libraries. I have routines for a tickler function. This has the computer prompt for when to contact customers based on a period, which period is adjustable by the type of customer, or individual customers. It is also a great candidate for using QiQ instead of the view that is currently used.
Data import and merge functions - A set of procedures to import a text file into a schema. The routines use the TEXT table feature of HSQL to import the data. To name two.
Contact / Customer management. This was a database created to help show how one might manage a many to many table relationship. It used 2 data entry forms and later a dialog as a splash screen. Later still I added a search form. The schema is fairly complete for customer information and event information. It includes a basic library that is used to launch the application, and uses a dialog box as a splash screen. Their is one report includes, a simple report but one that uses a query that includes embedded formatting. Showing how to create formatted multi-line column entries in the report.
This form is designed to be used by other forms, functions and includes a set of basic macros to be used to update its contents for display and to exchange data with the caller.
Order / invoice generation
The first two screens here are from a database that would be used on a laptop by a route sales person. The database schema is pretty well fleshed out with an emphasis on products, vendors, ordes and invoices.
Order Head ( New Order Screen ) [ Route sales company ]
Order Detail ( Order Line Items ) [ Route sales company ]
This next screen was for a database to be used in a small gift store. In this case the products are mostly one off items. There is lots of emphasis on seperating buyer from recipient as much of their business is with corporate buyers giving items as gifts. This schema is fairly complete for order, invoice and customer. It includes a couple of reports.
Order Entry Screen ( Gift Shop – so lots of different shipping vs Billing addresses )
This database is a bit different as some of the tables are not based on the schema that ships with Base. However the customer information is compatible. A couple of simple tables track the 'account' status for the customers that have layaway items. There is no reports with this database.
Store Layaway Screen [ Thrift Store ]
This was a database created simply to show how to handle business level transactions that require updates to more then one table. It requires that a basic procedure start it, this procedures then opens an isolated connection. This is connection is passed to the form on startup allowing for the basic code to handle the multi-table transactions.
Inventory Adjustment Screen
This invoice form is part of the database for the route sales. The invoices are based on a Calc template, the Calc sheet uses a collection user defined variables. A basic procedure creates a new invoice on the temptlate, then updates the value of the variables with those from the database records. Finally the invoice is saved as a pdf file to disk.
Invoice form as Calc template file.
Misc. This database has the least schema work done, the emphasis was on this one form.