==========1.1==========
Bug fix release: gun-1.1
As always, things won't work without the instructions.

This release fixes a bug in which changes were prevented from being saved because of a constraint placed on the ANT and CR columns in GUN_LOG.

If you're using version 1.0, then it's probably just easier if you follow these simple instructions on Page 2 to achieve the same bug fix.


==========1.0==========
Well, this is it! First, the instructions.

gun-1.0

It's exactly the same as RC6, so if you've downloaded that, then you're good to go.

ETA: If you prefer a hard copy bound book, here are a portrait (PDF) and landscape (PDF) template I made.

==========1.0 RC6==========
OK. Update. RC6. I wouldn't have done this, but I started a project page for this over at Sourceforge: https://sourceforge.net/projects/gun/

The download link is at the project page, linked above.

This is a minor update. Just has the "open image" button added. To restore a backup from an earlier version, extract the three files from your gun-*.tar.gz backup file, and overwrite the files by the same name in the gun folder with the files from your backup.


==========1.0 RC3==========
This is it! RC3 is here! Unless someone points out or I find some major flaw, RC3 should be the first release of 1.0.
gun-1.0_RC3.zip

Brief rundown of stuff:
1 - See the instructions in order to make it work.
2 - This database should be ATF-compliant for use as an electronic bound book.
3 - Is currently and will remain free.
4 - Cross-platform via LibreOffice (OpenOffice, too, but you have to install the Report Builder manually).
5 - In addition to the ATF reports (use the ATF_REPORT form), I've added a report to print all your guns.
6 - Automatic, periodic backups. You'll have to change the default setting in the BAK form. I use FreeOTFE to save encrypted backups to the cloud (in my case, DropBox). Backups are only made if a change is made to data in the GUN form, so you can also make manual backups using the BAK form.

==========1.0 RC2==========
RC2 is here! gun-1.0_RC2.zip

One last major feature update... The BAK form can be opened to change backup settings. Backups are only made if you're making changes to data in the GUN form. You can also hit the "Backup Now" button to make a backup. Backups are saved in *.tar.gz archives, which can be opened with 7-zip. You'll definitely have to change the path to the backup folder. I think it will default to your home folder, but I'm not sure.

Sort of a minor update: Guns marked as "Personal" will not be logged to GUN_LOG and will not show up in the ATF Printout or ATF Spreadsheet reports.

Enable macros (see the instructions) if you want all the features to work.You'd also better take a look at the instructions if you want it to work at all.

I'd also like to remind you that this database is and will remain free.

IMPORTANT: If things weren't working for you earlier, this might be the reason why. The instructions have been modified to reflect the fact that you need to register the database. This does NOT mean information is sent anywhere. This just means that the LibreOffice program keeps a local list/registry of databases, and in order for all the features of this database to work properly, it needs to be on this list. Basically, go to Tools > Options > LibreOffice Base > Databases > New > Browse > Open gun.odb and save the settings. The registered name must be gun.

All the bogus/testing data has been deleted.

The requisite screen shot:




==========1.0 Release Candidate 1==========
First release candidate!
gun-1.0-RC1.zip

I've greatly simplified the process for printing ATF reports per regulation. Just go to the ATF_REPORT form, enter the start date and end date of the date range you need to print, and click the button!

I've left the bogus testing data in there for now, but will remove it for the next release candidate (RC2). I hope for/expect RC3 to be the first *actual* release.

As always, it won't work without the instructions. Notes on ATF compliance.

I've polished up the different "categories" that can be associated with each gun to include Events and Maintenance events. Please check it out and let me know what you think!

Also, if you frequent any other gun forums, please let others know this is available!

Gratuitous screen shot:



And a screen shot of the Maintenance window:




==========0.9.9==========
Update! As always, it won't work without the instructions. Notes on ATF compliance.
gun-0.9.9.zip

You can now dynamically add sub-categories of the "All Miscellaneous" category. When you open up the MISC form (or click on "Manage" while viewing All Miscellaneous or a sub-category of it), entering your own category is mandatory so items will show up in lists. My next project will be to automatically reduce all caps to lowercase, except for commonly recognized abbreviations.

Just kidding. That'd be way too much work.

Anyhow, give it a run, and let me know what you think! Enable macros per the instructions if you want all the accessory stuff to work. Otherwise, version 0.9.5 doesn't have any macros.


==========0.9.8==========
Re-worked the accessories selection system and added a miscellaneous type.
As always, it won't work without the instructions. Notes on ATF compliance.
gun-0.9.8.zip

I've added an accessory "miscellaneous" to capture perhaps less common accessories. Ideally, though, each category of accessory should have its own specialized data entry page. Suggestions are welcome!

Here are some screen shots:


Just a reminder, please test things out, but don't go adding large amounts of legitimate data until version 1.0!

==========0.9.7==========
HUGE update! As always, it won't work without the instructions. Notes on ATF compliance.
gun-0.9.7.zip

From this version forward, the database will use macros. Why? Because some features that I've added (which I think are awesome) require macros. In particular, macros are needed to easily peruse and edit the accessories. Since this database is a work in progress, PLEASE test it out and let me know what you think! But you might want to wait until version 1.0 to start entering lots of data.

Screenshot of the accessories section:


The full main data entry page:



To enable the macros for this database, click on...
1 - Tools > Options > Security
2 - Macro Security >
3 - Trusted Sources > Add >
4 - Browse to the directory that contains your gun.odb file and gun folder (in my case, this directory is db in my home folder), and click OK > OK > OK then File > Exit (also exit the quick starter in your system tray, if it's enabled):


If you have no need or desire for the additional features that macros bring to the database, you don't have to enable them, or you can use gun-0.9.5.zip, which does not have any macros installed, but should still satisfy ATF requirements.


==========0.9.5==========
Minor update. As always, this thing will NOT work without the instructions.
gun-0.9.5.zip

Pretty much just cleaned out the sample entries.

Also, the latest version of HSQLDB is 2.2.6, which should also work just fine. If you're using 2.2.5, no need to upgrade the engine, but you can, if you want.



==========0.9.4==========
Important update! As always, the instructions.
gun-0.9.4.zip

ATFquery now selects (1) all guns in inventory and (2) guns disposed of/transferred during the specified time period. You only have to change one line. Change '2011-07-01' to the start of your date range (be sure to use single quotes), and change CURRENT_DATE to the end of your date range (using the format 'YYYY-MM-DD' including the single quotes). If the end of your date range is the same day as the day you're running your report, you can leave CURRENT_DATE as is.

WHERE DATE_DISP BETWEEN '2011-07-01' AND CURRENT_DATE



ATFquery Printout now labels all information fields, and can be used for the periodic printouts.

ATFquery Spreadsheet can be used as before, e.g., for the ASCII requirement (save as comma- or tab-separated values document).

Since both of these reports draw from ATFquery, just change ATFquery, save the changes, then open up one or both of these reports, as needed.


==========0.9.3==========
Update: gun-0.9.3.zip

Reports are much better now! Instructions for setting the date range for the reports are in the README.txt:

The reports have been improved and now can be set to included all guns acquired or disposed of during a time frame that you plug in. This makes printing the ATF-required reports much easier. The most difficult part is to set the date range. To do this, go to Queries in the main window, right-click on ATFquery and select Edit. There are two lines you need to change. For each line, change the first date to the start of your date range. Change CURRENT_DATE to the last day of your date range in the format 'YYYY-MM-DD' (be sure to use the 'single-quotes'), or if the last day of your date range is today (the day you're running the report), just leave CURRENT_DATE as is.

First line you need to change:
WHERE DATE_ACQ BETWEEN '2011-07-01' AND CURRENT_DATE

Second Only line you need to change:
WHERE DATE_DISP BETWEEN '2011-07-01' AND CURRENT_DATE



Then File > Save the query and File > Close, then File > Save in the main window.

Then click on Reports, and double-click the report you want to run.

ATFquery Spreadsheet opens a spreadsheet with the records from your date range. You can save this as a LibreOffice spreadsheet, or as a comma- or tab-separated values document. The latter (comma- or tab-separated values document) fulfills the ASCII format requirement. If you prefer, you could use this spreadsheet to print a "mail merge" type of report, otherwise...

PRINTquery opens a no-frills printable report of all records in the specified date range.

==========0.9.2==========
UPDATE! Unlimited pictures, print reports, audit trail, pre-generated list of calibers, cross-platform, free.
gun-0.9.2.zip
As before, follow the instructions on how to set up the HSQLDB engine and then the database itself.

Instructions to export data from an old version of the database and import data to a new version.

Version 0.9.2 - Multiple feature updates

Notably...

Please install the Report Builder extension if you use OpenOffice! It seems that at least the Windows version of LibreOffice has Report Builder pre-installed.

1. There are two Reports made with Report Builder that can be used to satisfy the ATF "print out" requirements. The PRINTquery report gives a no-frills printable version of the required data. The ATFquery report essentially exports the ATF-required data into an Open/LibreOffice spreadsheet. From the spreadsheet, you can save it as a comma- or tab-separated document, which satisfies the ASCII requirement. You can also do a "mail merge" type of print out of the bound book data from this spreadsheet, if you prefer doing so instead of using ATFprint. I actually wasn't able to get Report Builder to work with OpenOffice. On the other hand, it looks like Report Builder comes pre-installed with LibreOffice if you're using Windows. Unfortunately, I don't have a Mac, so I can't test Open or Libre Office on that platform.


2. Entering a new caliber stores that new caliber in the drop-down menu for future use. This feature is also enabled for some other fields.


3. A button has been added (but you have to make it functional with the CopyRow macro) so that you can copy a record and immediately edit it as a new record. For example, if you have 87 Glock model 19's all acquired from the same source on the same day, just enter the first gun, save the record, then hit Duplicate Record and Edit as New, change the Serial #, save the record, hit Duplicate Record and Edit as New, and so on. Each Serial # must be unique, and a Serial # must be entered for every gun record in the database. If they were acquired on different dates, remember to change the date, of course.
   
   
   To install the CopyRow maco, open CopyRow.txt (in the GUN_SQL) folder, select all text, and copy.
   
   In Open/LibreOffice, go to Tools > Macros > Organize Macros > Open/LibreOffice Basic. Go to My Macros > Standard. Click on New. Enter the name CopyRow for the module. In the window that opens, delete all text/code and paste the contents of CopyRow.txt. File > Save the macro and File > Close the window.
   
   Back in the main window, go to Forms, right-click on the GUN form, and select Edit. Double-click on the button Duplicate Record and Edit as New.
   
   In the Events tab, click on the [...] button for Mouse button pressed. Under Assign, click on Macro > My Macros > Standard > CopyRow > onBtnClickCopyRow and click OK > OK. Then File > Save the form, File > Close the form, and then File > Save in the main window.
   
   Now when you click on the Duplicate Record and Edit as New button, it will copy the current record and open it for editing. If you delete or do not enter a unique Serial #, you will get an error when trying to save the entry. If you decided you don't want to save the entry, hit the Undo Data Entry button before saving the new record:
   
   

==========0.9.1==========
Update: gun-0.9.1.zip As before, follow the instructions on how to set up the HSQLDB engine and then the database itself.

Added calendar drop-down menus for the dates. Also some basic format-checking (e.g., it won't let you put letters in at the phone number or ZIP code).




==========0.9.0==========
UPDATE! Actually, a significant update. gun-0.9.0.zip Changed the name from "guns" to "gun" to reflect the significance.

Cleaned things up substantially. Same directions for setting up the database apply to this version.

Probably the biggest noticeable change is that the tab order is "normal." This was accomplished, in short, by putting *all* gun data in the main "GUN" table. Only when UPDATE is called on ATF-required data fields are entries made into the "GUN_LOG" table.

You have to save the entry for the gun (initially) before you can add images to the record.




==========0.8.0==========
Sooner than expected, because it was easier than I thought! Here's the original thread.

guns-0.8.0.zip

Please let me know if there are required bits of information that this database doesn't record.



Be sure to read the "README.txt" file. The database won't work if you don't follow some of the directions in there. Specifically, you need to upgrade the database engine to HSQLDB version 2.2.5 and modify the path to the database itself. Here's the README for reference:


I'm releasing this database under the Creative Commons "Attribution-ShareAlike" license (Link) which basically says you have to attribute the work to me (tc2k11) if you redistribute it, you have to share it under the same license if you redistribute it or a derivative work, and it's not my fault if the SHTF for you because you used this work.