Foxfire!

Description: The Standard Developers Edition has the option as to whether or not you have to use the new User Management features of v6.0 (for backward compatibility reasons). To turn off the User Login requirement and the rest of the User Management features, you must use the Foxfire! batch cursor to start Foxfire!, and set the USE_LOGIN field in the cursor to False. See the Foxfire! online documentation for details on how to start Foxfire! using the batch cursor.

2. Adding a Preference Set using the Preference Set Editor

patch update: 03/28/2000
type: bug
overview: Foxfire! builds incorrect SQL for FoxPro databases and other misc bugs.
status: fixed

Description: You can add a new Preference using the Setup Wizard, or using the Preference Set Editor dialog. Adding Preferences using the Preference Set Editor results in various bugs because the Preference field PF_RMDTYPE (database type) is not getting initialized properly to the correct database type. A quick workaround if you have already created the Preference is to open the Preference Table, FFPREFER.DBF, and set PF_RMDTYPE to the correct database type.

VFP or FoxPro: "FOXPRO"
MS SQL SERVER: "SQL SERVER"
ACCESS: "ACCESS"
SYBASE ASE: "SYBASE ASE"
ORACLE: "ORACLE"

After applying the patch, you can create Preferences using the Preference Set Editor without problems.

3. Empty Data Item Picker

patch update: 03/28/2000
type: bug
overview: Data Item Picker Available List shows list of ".F." values
status: fixed

Description: If you select EVERY data item from the Available List in the Data Item picker, the Available list will show a list of ".F." values. The patch fixes this problem.

4. Foxfire! VIEW support

patch update: 03/28/2000
type: bug fix and enhancement
overview: Foxfire! v6.0 does not implement Foxfire! Views properly
status: fixed

Description: Foxfire! Views allow you to partition your Relationships in the Relationships table to resolve problems with implementing complex data schemas. Foxfire! v6.0 new Join Tree architecture did not adequately account for Foxfire! Views. A View Changer has been added to make it easier to implement and visualize Views. The Request Wizard has been fixed to show available Views, and the SQL engine now properly uses the the specified View.

5. Foxfire! Join Tree simplified

patch update: 03/28/2000
type: bug
overview: Changing Sibling Order with complex Join Trees causes OLE error.
status: fixed

Description: The Join Tree allowed for specifying how sibling nodes would be orderd in the generated SQL. The whole Join Tree mechinism has been simplified by removing the ability to change Sibling Branch order and using a simple Alpha order instead. This allowed for the use of a much simplier Join Tree building algorithm. Thanks to Serge Matsevilo for taking the time to help debug these Join Tree problems and providing a much cleaner Join Tree builder algorithm.

6. Foxfire! v6.0 for VFP 5.0 freezes in the Request Manager

patch update: 03/28/2000
type: bug
overview: Using F1 - Help or F8 - Comments causes Foxfire! to freeze
status: fixed

Description: Foxfire! v6.0 uses ActiveX controls in the Request Manager. Errors occur if any forms are launched modal from the Request Manager in VFP 5.0, so the F1, Comments, and Request Tree maintenance dialogs have been removed from the VFP 5.0 version until a fix can be found. It is highly recommended that you upgrade to VFP 6.0 if at all posible if you use Foxfire!.

7. Support for British Date settings

patch update: 03/28/2000
type: bug/enhancement
overview: Foxfire! errors when running queries with date filters and the date setting is British
status: implemented

Description: Foxfire! now supports using British Date settings.

8. Fix Support for British Date settings

patch update: 04/06/2000
type: bug/enhancement
overview: British DateTime data types not handled properly
status: fixed

Description: Both date and datetime data types now supported with "SET DATE TO BRITISH"

9. Typo in Data Dictionary for DateTime data type

patch update: 04/06/2000
type: bug
overview: Data Dictionary data type combobox has typo for datetime data type
status: fixed

Description: Combobox fixed to say "datetime" instead of "datatime".

10. Setup Wizard change alias error

patch update: 04/06/2000
type: bug
overview: Changing the Alias name when loading tables using mixed case causes errors
status: fixed

Description: This bug only occured for VFP tables. Changing case of the Alias name of a loaded table should not have been allowed for VFP tables. All previous versions have forced uppercase. Only ODBC tables can have mixed case names since many ODBC backends are case sensitive about names.

11. Cannot update Join Tree error

patch update: 04/06/2000
type: bug
overview: When aborting a Setup Wizard session, error occurs if Relationship Editor entered.
status: fixed

Description: If you accidently started a Setup Wizard session, then went into Relationships Editor, the Preference record is positioned on the wrong record causeing the Relationships Editor to build a Join Tree from another Preference.

12. Garbage in FFREQMGR class methods

patch update: 04/06/2000
type: bug
overview: Foxfire! build out process introduces garbage in FFREQMGR class methods
status: fixed

Description: This didn't seem to cause any problems on rebuild of the app, but in any event the VCX's are clean now.

13. FFFORM class changed to default the ShowWindow to "in top level form"

patch update: 04/06/2000
type: redesign
overview: Foxfire! integrates better with "in top level form" setting
status: implemented

Description: Thanks to Erik Moore for this suggestion.

14. Some Foxfire! messages displayed in German

patch update: 04/06/2000
type: bug
overview:
status: fixed

Description: Foxfire! messages are data driven, and some German strings got accidently inserted during the English language built out process. Foxfire! code is localized so everytime there's a new build, and English version gets generated from the codebase.

15. AARCMDOK/AARCMDCANCEL classes removed from FFAARCTRLS class

patch update: 04/06/2000
type: redesign
overview: Unused class removed
status: implemented

Description: Unused class refered to another removed class.

16. Replace Andale Mono font with Foxfont in all Listboxes

patch update: 04/09/2000
type: redesign
overview: Replace Andale Mono with FoxFont
status: implemented

Description: Installation of Andale Mono required manual installs in many cases. Use of FoxFont makes distribution and installation much easier.

17. LONODE is not an object

patch update: 04/25/2000
type: bug
overview: Error when adding Relationship to empty Join Tree
status: fixed

Description: If you hadn't selected the root node of the empty Join tree, then added a relationship, you get an OLE error that LONODE not an object.

18. Change output "to file" name not saved

patch update: 04/25/2000
type: bug
overview: Changing the output "to file" name not saved when exiting the Output screen.
status: fixed

Description: The Output "to file" name textbox was left enabled allowing editing the output file name. Instead the Output "to file" name should only be change by select the "File..." radio button.

19. Missing semi-colon in Show Sql statement (FoxPro SQL)

patch update: 04/25/2000
type: bug
overview: Displayed SQL in the Show Sql dialog missing semi-colon.
status: fixed

Description: You should be able to cut-n-paste out of the Show Sql dialog. There was a semi-colon missing from the last Fields list item. This would make it so you would get an error if you ran the SQL in VFP. The semi-colon has been added.

20. Long data dictionary report expressions truncated

patch update: 04/25/2000
type: redesign
overview: Data Item Expressions longer than 254 truncated.
status: implemented

Description: Even though the data item expression is maintained in a memo field, previous versions of Foxfire! have always limited data item expression length to 254 characters. This was partly because a @GET textbox was used to the expression in previous versions, and partly to control the SQL line too long errors that were frequent in earlier version of FoxPro. The expression is no longer truncated, and can now be edited with an Edit box.

21. Privileges to disable Summary and XTAB reports not working

patch update: 04/25/2000
type: bug
overview: Disabling the Privileges to create Summary and XTAB reports doesn't work.
status: fixed

Description: You can control access to many user interface features through the use of Privileges. The Summary and Xtab report Privilege flags were not effecting access.

22. PG_FFABOUTS flag not respected

patch update: 04/25/2000
type: bug
overview: Removing About FF from menu not working.
status: fixed

Description: You can control whether or not the About FF! menu item appears on the Tools menu using the flag PG_FFABOUTS. Setting this option to FALSE in FFCONFIG will cause the Abouts FF! menu item to be removed from the menu.

23. Edit Report Layout privilege not respected

patch update: 04/28/2000
type: bug
effected source: ffforms.vcx
status: fixed

Description: There are two locations in the interface where users can edit the Foxfire! generated report layout. One in the Request Output options dialog, and a second in the after Preview dialog. There is a privilege to control access to this option in those two locations. The after Preview "edit layout" button wasn't properly disabling when the privilege was turned off.

24. Program FLT_DEL does not exist

patch update: 04/28/2000
type: bug
effected source: fforms.vcx
status: fixed

Description: FLT_DEL method makes reference to old FLT_DEL procedure, which has been moved into method code in v6.0

25. Display Warnings dialog displays behind Preference Set Editor dialog - can't exit

patch update: 04/28/2000
type: bug
effected source: ffprefee.prg, ffmsgtxt.spr
status: fixed

Description: When saving changes to a Preference in the Preference Set Editor, if there are warning messages, they get displayed in a dialog. Since the Preference Set Editor still uses .SPR's, there was a problem due to display message dialog being a form class. The old FFMSGTXT.SPR needs to be used in this one instance instead.

Micromega Home