WELCOME
Welcome to the beta release of Windows Genealogy Version 2.xxx!  Copyright Jim Blaich, 1995.

This file contains an explanation of the purpose of this beta release.

Windows Genealogy Version 2.xxx beta is being released in order to allow those interested to gain an inside look at the direction of Windows Genealogy development.  It is also provided to give you an opportunity to make recommendations about what can be included in the final release and to provide me with bug reports, bugs that are difficult to find or are time consuming to run down.


INSTALLATION
To install the Windows Genealogy program use PKunzip or some other de-archiving (WinZip 5.6 (and later versions) by Nico Mak Computing is a good alternative for Windows users) utility to extract all the .zip files into a directory of choice.  For example: unarchive the files into a directory called Wingen.

c:
cd\
md wingen
cd wingen
pkunzip a:\wingen*.zip c:

Repeat the pkunzip statement for each of the archives.  The above sample assumes that you are picking these files off of drive A:.  You can do the same by referring to the files located on any of the drives.  Additionally, you can store the files into any directory on any drive.  Such as h:\genealgy or d:\wingen or c:\wgn or I:\apps\wingen, etc.


DISCLAIMER/RESTRICTIONS
This beta release is not free.  If you use it, and continue to use it beyond the 15 day trial limit, you are bound by registration requirements; listed in the Help file.  You can view the registration requirements and copyright notice by examining the wingen.hlp file using the winhelp.exe help file viewer: examine the registration and copyright help topics.

If you are interested in the program you can register the product by sending a letter and a check or money order for $65.00 made payable to only JIM BLAICH.  The address is: 1808 Oak Park Blvd, Suite 17, Pleasant Hill, CA 94523.

NOTE:  There is NO GUARANTEE that any of the data input into this version of the program will be useable when the final release is made.  The structure has been set and should NOT undergo any changes, but there is always a chance.  I DO NOT anticipate any structure changes to the data file, but just in case this warning has been presented!

Note:  To registered users this update is free (in the final release form).  It completes update number 1.

This program uses the updated Access JET engine .dll files.  You can accidently overwrite some older .dll files (for instance, if you have only Access 1.1 or Access 1.0 installed) (Note:  you are not in any way required to own MS Access or any other Microsoft product (except Windows) or any other company's product to use Windows Genealogy (except DOS)).  If by chance you do have Access 1.0 or 1.1 or any other application that also relies on the MS Access JET engine or other products you will need to make sure you do not cause any problems for them.  Your best bet is to unarchive all the files into the Windows Genealogy directory of choice, regardless of whether these files may duplicate other files in other directories.  You should only ensure this if you are sure you will not be outdating other files, otherwise, you can feel free to move these files to the directories of choice.  (Remember, the support files, .dll and .vbx, etc must be located in a place where Windows Genealogy can find them.  You safest bet in most cases is to leave the files all located in the same directory as the executable (wingen.exe) and other support files (*.cnf, *.mdb, etc.).  If you fail to ensure this I am not responsible for the problems that may result nor do I expect to be looked upon as not having a good solid product.  Virtually every program has these requirements.


KNOWN PROBLEMS
Because Windows Genealogy 2.xxx is being released as BETA it is known to have some problems.  Although the list of problems is probably beyond the scope of this document, I will list some known problems.  Below is that list.

* The biggest problem with the program is that all previous file formats are completely incompatible and there is no conversion utility for fixing the file format to make it compatible.  NOTE:  If you are a registered user I will be more than happy to convert your data for your if you are willing to exchange that data with me through the internet (you will need to provide me with the ftp internet address where this data can be picked up and stored once updated).

* Note:  Any additions to the names (first and middle, surnames, and places) listings will be lost.  As well, all additions to occupations, eye colors, hair colors and the like will be lost.  The wingen.mdb file holds this information.  It has extensively been updated to hold those catetories of information and much more.  I appologize for this, but continued use of the program should result in these additions showing up.

* If you run share.exe AND vshare.386 TOGETHER you will run into problem where the system will report that a closed file is "already in use" and cannot be opened.  This is a MICROSOFT bug and not mine (there may be fixes to this that I am not aware of).  Be sure that you correct this by removing the redundant statement from your config.sys, autoexec.bat, and/or system.ini statement.

* When using large buttons for the toolbars, under Windows 3.x, two toolbars do not resize correctly on the program load.  To correct the problem switch between the large to small buttons and then back.  This is a bug in the Sheridan Software's Designer Widgets tools and is not a fault of mine nor any lack of effort on my part.  This is not a problem with Windows NT 3.xx.  Optionally, you can elect to simply stay with the smaller toolsets.

* When compacting a data file, and you experience a problem, you can loose the whole data file.  Please do not compact your data files without first doing a repair.  It is further recommended that you not compact the data files at any time unless you have a backup of your data file.

* The descendent tree is not altogether capable of updating itself completely.  This means that there are times when some names will not show up in the tree after these names had been just added (and they would normally be displayed in the descendent tree).  You can regenerate the tree by closing the descendent tree form and then reloading.

* The descendent tree has a problem where whenever an individual is added just below another individual, as the top individual in the sub-branch; the name is not displayed.  The name can be displayed by collapsing the branch and then expanding it.  This is a known bug caused by MICROSOFT.  They have been contacted and have ignored my request to complete a fix.

* There are known to be crashes when exiting some forms.  I've had the system give me a GPF when saving and closing the military, sources, and physical/medical forms.  Under Windows NT 3.xx this is not a problem; the crashes do not occur.  I suspect this is a bug in Microsoft's ODBC drivers.  If you experience these problems, please let me know.

* Not every last individual can be deleted from the data file.  There are limits to who can be deleted and under certain circumstances it is impossible to delete every last individual.  If you want to delete everyone please recreate the file using this same file name.  If you are only attempting to delete to a specific point you may be better off recreating this file.  It should be known that it would be very rare that there will every be a need to delete everyone, or hopefully anyone.

* When importing GEDCOM files into Windows Genealogy the Family Notes table is not updated properly.  The end result is that you cannot enter family notes for these imported GEDCOM files.  The final release will have these problems resolved.  **** fixed ****

* When importing some family member's via the GEDCOM import some family member's, that should be marked as being formally married, are not marked properly.  Select their marriage section and click on the formally married check box and save the two records.  **** fixed ****

* The time fields have some problems in formatting.  Use the default, and enter the times in military time, and you should not have any problems.

* Some form icons are missing.  Ignore these missing icons until I can recreate them.  *** fixed ***

* "Fully Restore Last Environment" is not working completely.  At present it will restore locations and sizes of windows, etc.

* It is not possible to build an ancestor tree.  You may build a tree on an individual and then step back through the tree based on any individual including the spouse of an individual.  Do so by selecting the individual (and/or the spouse) and select to step back (ctrl+B) (or ctrl+I to build on the spouse of the individual and then use the ctrl+B to step back from that individual.) The tree should build quickly.

* Report generation is still very weak.  Provide me with report layouts and I will attempt to create them.

* The query form is a very complex portion of the program that allows you to perform some extremely complex sophisticated lookups of data about you family history.  Experienced users should only attempt to used it.  NOTE:  it is not possible to create a query and then edit it back in the query builder.  You may make modifications directly to the query string if you are experienced enough, and then you can save the query again under a new name or by deleting the existing query (after copying the SQL statement to the clipboard) and then pasting it into the SQL text box and saving it under the same name.  *** many fixes ***

* At times the query you create is not built correctly by the builder.  Most of the time it is because you have a comma at the end of the SQL string that does not belong.  Clear this up and most of the time you will be able to execute the query and save it. **** fixed ****

* If you get an error 381 when executing a query that was just built copy the SQL to the clipboard, then click on an existing query to view it's SQL statement then select the new SQL statement and paste the newly created SQL statement over the stored SQL statement.  You will not cause any harm to the existing pre-stored statement.  You can still save the new query under a new name.  *** fixed ***

* You cannot store a query into a different file (in future versions this will be added to the program. (At least to allow you to store new generic queries into your struct.cnf file.)  *** fixed, better implementation incorporated ***

* It is best to store query names without spaces in them, just in case you need to use the query as the basis for another query (which is possible).  If you do make sure you enclose the name of the query in brackets [], e.g., [Parents and Children].  Alternatively, you could store the query as ParentsAndChildren.  *** do it your way ***

* Note:  The current date format is stored in a variable called editformat and the current time format is stored in a variable called timeformat.  These can be used in your SQL statements.

* If you have serious problems on startup that seems totally unexpected, which I can say will be very rare, delete or rename the wingen.ini file and reload the program.

* If you receive the error that ctl3dv2.dll is not installed correctly on this system remove the ctl3dv2.dll from your Windows Genealogy directory by renaming it or deleting it.

* If you receive a message about balloon help failing to create a popup window this is a problem caused by low system resources.  Close the program, close your other programs, and restart windows and then Windows Genealogy.  Do not restart those other programs.  It is a problem that has been reported to WEIMER Software about a year ago and several updates ago.  They have not fixed it yet.

* Once in a while you will not receive the correct mouse cursors.  This is also an indication of low system resources.  This is a bug in Deasware's custom control for mouse cursors (CCF Cursors).  I have reported the problem to them and they have denied it.  They have denied things in the past and then gone back and fixed them.  Hopefully, they will fix the problem.  There is no fix for this at this time.

* Military's place of discharge is not looking up in the listing.  Will be fixed in the final release. - low impact bug.

* Place of divorce is not performing a lookup in the listing.  Will be fixed in the final release. - low impact bug.

* There is no way to edit the family notes based on the second spouse of the family member.  This will be fixed in the final release.

* When deleting the spouse of a family member there is a bug that can cause problem.  Do not delete the spouse of family members at this time.  This will be corrected in the final release.

* When selecting wars, diseases, awards, and records from their respective form's listings you will need to first select the list item by clicking on it, then fill in the information relevant to that selected item and then click the add/update button.  If you move to another item in the listing the edits will be lost.  There is no solution to this at this time.  Hopefully the next official release will have solved this problem.

* The ages of individuals, examined in the about family member dialog, does not always calculate correctly.  Hopefully, in the final release this will be corrected. *** fixed ***  *** + a age calc has been incorporated ***

* Some help topics are not complete.  The file has been extensively updated but some areas are still not up to date.  Some of the pictures of the forms are out of date.  These also will be updated.

* When adding children to a parent listed in the descendent tree the tree count is not accurately calculated.  This can be recalculated by regenerating the tree and then re-expanding the tree/branch.  Not a big bug.

* In high color modes (35K+ (or greater) number of colors) visual basic cannot handle drag icons correctly.  These will appear black, all through.  This is a problem created by Microsoft and their is no cure at this time.

* When dragging from the Individual Listing ensure that you have grabbed the correct item.  It is possible to have meant to grab one item but only have grabbed an item right next to it.  This is a problem with Visual Basic, moreover with Windows itself.

* When performing a search for the first time in the individual listing and then removing the search list box the 3d effect does not restore properly.  Minor bug. *** ? Fixed ***

* Sometimes, under very rare circumstances, the second and additional spouses for a family member, listed on the spouses flyout menu, are not properly cleared so the name of some of the spouses are not appropriately listed.  Close the program and reopen it.  This bug is caused by Windows.  Windows, when attempting to create a new menu via loading an object, when a drop down list is displayed will generate an error, likewise for deleting a menu via unloading the object.

* Will loose the right mouse tear off menu for the desktop after docking any toolbar.  This is a Sheridan Software bug, which will hopefully be fixed with their next release.

* Sometimes when you have restored a session after having the main window in a normal (not minimized and not maximized) state the toolbars will sometimes not be visible.  Make them invisible and then visible again and they should show backup.  If they do not you can edit the wingen.ini file for that specific toolbar and change it's left and top properties to 0 or some other reasonable amount.

* Dockable toolbars do not always end up in the same place they were when the program was shut down.  They will normally be in the appropriate edge of the window but may not be in the same order on that edge that they were when the session was closed.  This again is a Sheridan Software bug and it also has been reported to them.  They have stated they are working on a fix for this.

* When using the help outline the outline experiences the same problem when adding and moving items in the tree as does the Windows Genealogy program.  The reason is they are based on the same Microsoft tool.  The MSOUTLN.VBX which has a reputation throughout the industry as being buggy.  Microsoft has made absolutely no committment to fix this type of problem for us developers.  The good news is that Windows 95 and Win NT 3.51 incorporate an outline stock object right in the environment.  This should resolve any problems with this upon the next official relese of Windows Genealogy (probably Windows Genealogy 3.x).

* When calling up the help file and you select the "Launch Outline" menu item the help outline will be launched and it itself will probably load a second copy of the help file.  Close down the first copy and use the second copy loaded by the Help Outline.  I will do whatever is possible to fix this in the next release of Windows Genealogy.

* When selecting to customize the toolbar, by selecting the customize menu from the toolbar menu the toolbar customize tab in preferences is not presented the tree configuration tab is.  Switch to the toolbar configuration tab by clicking on it.  This is a very minor bug and will be fixed in the final release. *** fixed ***

* The menu help location options are not implemented.

* "Add Child via Add/Edit Form's Child Grid" option is not implemented.

* Not all balloon help messages are totally accurate and not all controls have balloon help implemented.

* Single click on F1 label on function key bar brings up the help file but it does not retrieve the correct help topic resulting in topic not found message.  A minor bug.  Will be fixed prior to final release. *** Fixed ***

* The actions toolbar buttons are not enabled when "Last Used File" is selected in the preferences.  Minor bug with big impact.  Will be fixed before final release.  Causing a form activate event will cause the buttons to become enabled or closing the toolbar and then reopening it will enable the buttons. *** Fixed ***

* Sometimes not every item in the individual listing is colored correctly when changing colors for that form.  It is a small bug and it is caused by the MList 4.5 author.  Closing the individual listing and then reopening it will cause the colors to color correctly.  **** fixed **** **** removed feature ****

* The verticle grid line is not colored when changing colors.  Probably for the same reason as the bug stated above.  Closing the form and reopening it will cause the color to change appropriately.


RECOMMENDATIONS
Please limit, for the time being, opening forms to having one open at a time (excluding that one form, the trash, significant dates, the individual listing, the frequently used places/names listing, and the descendent tree).  MICROSOFT's visual basic program files are resource hogs.  I've put an ENORMOUS amount of EFFORT in minimizing the resource requirements, but still, what can I say, I cannot control Microsoft.

Run your system in at least 1024x768 video resolution with at least 16 colors (256 preferred).  You'll appreciate the added room and you can spread out.  Highly recommended!

Report to me your system configuration when you are reporting problems.

Feel free to give me any recommendation that you might have to make the program more useful.  If you send recommendations, such as new report formats, export/import from PAF or the like include copies of those layouts and the file formats or any documentation that will provide me with the most effective method of implementing those changes.  Any changes made as a result of your recommendation will be noted in the help file under acknowledgements.  If you send bug reports you need to tell me what you were doing and whether you can reproduce the problem consistently.

If some files are missing from the archives you should know that I took great care to ensure that all the necessary files were included in the program.  When the archive files went to the internet they were all there.  There is a disclaimer to all concerned within the archive that restricts anyone from altering the archives in any way.  Although this is the case, some BBS sysops have in the past removed files from my archives because they believed they duplicated files already on their BBS.  Most of the time the files that they have removed were the ctl3d.dll and the vbrun300.dll.  Although this is a violation of the distribution requirements I have had little recourse against these sysops.  It is recommended that if files are missing that you check out the internet and the BBSs in your local area for the missing files.

Use Help Outline to better examine the help file.

Have Windows Genealogy always restore last environment.

For those who insist on using lower video resolutions close down all extraneous visual objects such as the status bar, the function key bar, the toolbars.  Since the screen is wider then it is taller try docking toolbars to the left or right side of the window.  You may also desire to maximize all child windows to get the best overall perspective of the forms.

OTHER
The *.ldb files are created by the Access JET engine which is the object oriented relational database engine used with Windows Genealogy.  These files can be deleted at any time that Windows Genealogy is not loaded or the related data base file is not loaded.

Do not delete any of the *.cnf files nor the *.mdb files.  The *.tbr files are for toolbars and they should not be deleted.  None of the files in the system should be removed at any time, at least without prior clearance from me.

The *.oli files are for the ouline files used with the Help Outline program.

There is no guarantee that the Help Outline alterations work.  You should simply use the outline as is.  It is not complete.  It is only as complete as the help file is, which has already been stated to be incomplete.

If you do send me any type of response, and you have an internet address, please send it.  This will more easily facilitiate sending you replies and updates.


REGISTRATION
Once you register the program you will receive the all that is necessary to remove the NAG portions of the program.


Sincerely,


Jim Blaich


Note:  All rights are reserved.  All third parties mentioned in this file are considered to have their own legal rights to their product.  I claim no rights nor reserve any to their products except as implied by any liscensing agreements between them and myself.