UserBase Whats New:
Known Issues
- Only the Internet Gateway is automatically excluded - other gateways need to be added to the skip list to ensure they are not extracted out to the database (this will not cause a problem with the application, but the gateway information is mostly useless).
What's New
v2.50
- Userbase manual and online help added
- Added support for the new FC7.10 fields
- UserBase Source Code now supplied
- Add support for "Human Readable" Date & Time
- New ZFields for RUFree application
- Updated Settings File.
v2.00
- Userbase table and field changes
- Settings table renamed AppSettings
- Lock renamed 3rdPartyLock
- Userbase20.fcx created to add backward support for RAD 2.0
- Userbase manual and online help added
- Added support for the new FC7 fields (Time Zone and Mail Import)
- Added support to extract Preferences ad Mailbox Import details
v1.33
- Added detection routines to check if a Privilege Group is added while UserBase is running. A bug in pre v2.1 RAD releases causes an array overload if a PG is added; causing UserBase to stall. If a PG is added, this version of UserBase will continue to queue user changes, but won't process them until UserBase is restarted.
- UBRestart is a server application that checks once a minute to see if a Privilege Group is added while UserBase is running. If so, UBRestart unloads and reloads the UserBase application.
v1.32
- Added a database upgrade routine so that databases version 1.20 or higher will automatically be updated to newer formats. This saves sites from having to install a new .mdb file and resynch.
- Added support for Z Columns. Columns beginning with Z in the Userdetails table are ignored by the field loader routine. These columns can be used for non-field related features such as presence indication etc
- Added the ZLogInOutState Column in the UserDetails table.
- Changed the Action state values in the Queue table. If the Action value is less than zero, then this means the login state needs to be changed for the user e.g. -2 indicates a user has logged in, and their account been modified and login status tracking is on.
- Add an Action value of 0 to indicate a login or logout event . This will only be added to the queue if Force Check is set to either Yes or Online. If set to Yes, the login value will be -1 (force check on login and update the ZLoginOutState column).
- Added support for flagging when a user is online. When activated (by setting Force on Login to either Yes or Partial), when the user logs in, the their corresponding ZLogInOutState field will be set to 1. When they Logout it will be set back to 0.
- Added Purge Login/Logout status routine to the Purge button in UserBase Monitor
- Fixed a bug in the Userbase Monitor where the Console Logging and Login Check flags were always being reset to default.
v1.30
- Added a fix to stop a Rad crash occurring when there are already pending login attempts at server startup
- Converted the Userbasedb.mdb file back down to Access 97 compatability
v1.29
- Added "Server version" support to the UserBase database, and included the new fields for the FirstClass v6.2 server.
Note: In order to support the addition of new information fields on the User Preferences form, the Userbase.mdb database had to be sigificantly changed. Notably, all the fields in the UserDetails table have been renamed. While most of the v6.2 fields have been added to the database, several of them (mainly the Time Zone related fields) are still not available from Batch Admin. Also, UserBase won't start "extracting" the contents of them until a Server version of 6.2 or higher is detected.
- Added a new "lock" routine to enable third party applications that have a lot of processing to do against the database to "lock" off the database for queue updates from the UserBase application.
- Removed an obscure occurance where in v6 servers some 3rd party applications were processing updates twice. This was due to Batch Admin reporting having been introduced in FC v6.0. Pre-v6.0 servers will still work as long as the steps in the developer manual describing how to trigger a queue update are observed.
v1.28
- Added support for user POP mail account details. Requires a 6.108 or higher FC Server
- Fixed bug that would only recognise an excluded Privilege Group if the case matched in the skip list i.e. no longer case sensitive.
- Removed support for pre-RAD 2.0 (FCAS)
v1.27
- Apostrophe handling still wasn't right. Apostrophes now converted to a \+ combination
v1.25
- Privilege Groups can now be added to the skip list. Any users belonging to an entered group will not be added to the UserBase database.
- Changed handling of apostrophes in user information. These are now translated to double apostrophe (the %60 interfered with the LIKE SQL statement) on the fly.
v1.20
- Removed a bug that was causing every second queued item to be skipped, so multiple queue cycles were needed to completely update.
- Fixed handling of apostrophes in user information. These are now translated to %60 on the fly.
- optomised many of the subroutines (now functions) for RAD 2.0
- rewrote the list extraction routine so that lists of user information containing more than 255 characters are captured in their entirety
- Rewrote the Synch routine to use the Diskuse.txt as the source for user ids (thanks to Jonas O. Djärv for this idea). Note that a synch request shouldn't be initiated while a Trash Collection is in progress, and the Diskuse.txt file will only be accurate if the Trash Collection completed successfully.
- Fixed a bug in the database file that caused the UserBase application to crash if the user account being extracted didn't contain an entry in the First Name field.
v1.11
- Added backwards support for FCAS 1.317 to both UserBase and UserBase Monitor
- Changed the purge options in the Monitor to allow the Queue to be purged without also purging all existing records
- Conferences and Gateways are now automatically filtered out of the UserBase queue i.e. they don't have to be added to the skip list.
- Changed the description on the Monitor form to reflect the above changes
- Changed the default Skiplist generated on the first time run to reflect above changes
- Removed the (accidental) "Refresh Interval" drop down list on the Monitor form.
| 