This database system was developed in 1992 using the DOS version of the Paradox database program. A Windows based follow-up program, named OK4H, is currently under development.  Both are a collection of database tables, forms and reports with a series of scripts used to navigate among the various options available. The All-In-One system can be broken down into two distinct parts:

• Paradox Runtime (version 3.5)
• All-In-One database files (version 1.9)

The two parts are stored here as self extracting executable files created using the compression program PKZip. To download them,  click on the link for the file you wish to download and select "Save to Disk" to save a copy of the file to your computer. To extract the files from the compressed file, run (or execute) the downloaded file. It will uncompress the files into the directory where the self extracting executable file is stored.

A DOS batch file (allinone.bat) has been created that can be used to run the database system.  This batch file will change drives to your C: drive, change directories to the default directory, and issue the command line to start the Paradox Runtime program using the first script in the All-In-One system.  If you invoke the batch file with the install option, by typing allinone install, the batch file will handle the installation process for you -- creating the directory and unpacking all of the files for you.  It also starts the program, to be sure it is working.

Windows95 throws a couple of wrinkles that DOS and Windows3 didn't have ... when you run DOS based programs and batch files, it suggests that the program may not run well unless the machine is restarted in DOS mode and offers to create a shortcut for you.  Do not let it create the shortcut for you -- the installation process should only be run once so there is no compelling reason to create a shortcut for it and the time required to shut the machine down and restart in DOS mode is not worth doing each time the program is invoked.  It also hides the shortcut in hard to find places on the Start Programs menu.

The command line to run the database system is pdoxrun access, but you may need to specify the name of the directory where the program is stored in order to get the program item (Windows 3.x) or shortcut (Windows 95/98) to work properly. The Paradox Runtime files can be stored in a different directory, as long as that directory is in the computer's search path.

Although the files can be installed in any location, by tradition/convention the current version of the program is installed in the directory c:\allinone -- this directory may need to be created, especially if All-In-One has never been installed on the machine. Versions prior to 1.9 were installed in a named directory "allin1" but this was changed in the Fall of 1998 to allow counties to install the new version without overwriting files from the previous version.

The database files posted here contain data from a sample set created several years ago.  You will need to load data about the clients in your county from an export disk or create a blank set of data.  If you have a disk created using the ES237, Export function of the program, copy the 10 files with your county's ID number from the floppy disk to the directory where All-In-One has been installed.  If not, change directories to the directory where All-In-One has been installed and type copy *.00 *.xx where "xx" represents your county's two digit ID number.

Once you have your county's data files copied to the program directory, you are ready to have the program change county ID numbers and begin entering data for your county.  To change ID numbers, select Setup from the main menu and then select  County from the setup menu.  Press the F9 key to edit the value and use the backspace key to delete the value "82" and type your county's ID number.  If you prefer to lookup your county's number, press the F2 key to display a list of county ID numbers and county names, highlight your county and press F2 to select it.  Once the new value is entered, press the F2 key to save the change and the system will write out a copy of the data in the tables and read in the data from the files for your county.  All entries made from then on will be enrolled under that county's ID.

If you are starting from scratch, be sure to enter the information about your clubs before entering information about your clients.  A side effect of the layout of the member enrollment screen is that the first field is the club number and it is required to be filled in before you can do anything else -- including exit the screen.  There is a validity check for a valid club number to ensure that the club exists and if there are no records in the club table, there are no valid club numbers and there is no way out of the current card without restarting the computer or ending the task.  This invalidates the stored index and locks you out of that table until you rebuild the index.

If you have entered club information and wish to stop entering cards, fill in a valid club number and then press the escape key (Esc) to exit without saving the last card.  Pressing F2 will save the card with just the club number filled in and throw off the number of members listed for that club.  It also throws the statistical counts out of balance because none of the statistical data has been entered.

A new section of the program was added a year or two ago for compiling annual end of year data.  The menu item to access it is "ES237".  Your first option is whether you want to enter data (DataEntry), report on data that has already been entered (Report), or copy the data to disk for sending to the state office (Export).  The data can be entered into one of three tables: Youth Group Enrollment, Volunteer Enrollment, or Leader Training.

All reports can be sent to either the screen (for examination) or to the printer (for historical record).  There is a problem with the reporting ... versions of DOS newer than 5.0 will crash when the report is sent to the printer instead of the screen.  The problem has no solution and very few workarounds.  One would be to move the program to an machine running an older version of DOS, but that isn't always possible.  A second alternative is to transcribe the results from the screen, but that could lead to transcription errors.  A final choice is to use the "Print Screen" feature to take snapshots of each screen of data, but that isn't very practical.

Contact Information