We are pleased to announce the release of PhonePad Version 4.24 (4.24.0.1). This is a maintenance release that addresses a number of important issues:
- An issue was identified where PhonePad would start with no user account when PhonePad was not configured correctly. In this situation users, were taken straight into PhonePad without logging in, but they were unable to send or receive messages and the Address Book was blank (this was because the user wasn’t actually logged in). Code has been added to check for these inconsistencies in the configuration and to prevent this from happening. In addition, PhonePad will in most cases tell you how to fix the problem. These errors are now also logged to ErrorLogViewer.
- A lot of error handling built in to PhonePad had suddenly stopped working due to an obscure bug. This has been fixed.
- The configuration checks within DBConnect have been expanded with some additional checks and more detailed information on how to correct any issues. The interface has also been improved and it’s now possible to print out the configuration checks so you have something to work from. In other words, if DBConnect finds some things wrong with your PhonePad configuration, you can print a hard copy (or export to PDF) of what is wrong and how to fix it (or you can send it to us so we can tell you how to fix it).
- Some users have been experiencing Access Denied errors when trying to save settings in DBConnect, due to over-restrictive Windows permissions. To get around this, all applications in the PhonePad suite have been changed to allow the configuration file (PhonePad.ini) to be located in one of a few different folders. Where the Access Denied errors occur, DBConnect will automatically and transparently store the configuration file in another folder. All PhonePad applications now know how to locate the file so this should happen without any user intervention.
- A problem was discovered with opening text messages (not to be confused with SMS messages) in the Sent folder. Due to a bug in sending text messages, the messages would be successfully sent but the copy of the sent message would be missing an internal identifier, preventing the message from being viewed. This has been fixed.
- When PhonePad was run in Remote Mode (aka client/server), if the connection to the server (DBServer) was lost PhonePad would appear to freeze or hang. In fact, what was actually happening was that PhonePad was continually trying to reconnect to the server. This behavior has been changed so that PhonePad will try to automatically make 5 reconnection attempts and then tell the user that the server connection has been lost. The user will be given the option to attempt again or to close PhonePad.
- The PhonePad installer has been modified in an attempt to make it a little less confusing when installing PhonePad. The Installation Guide has been updated in line with these changes.
- Searching for text in the Subject field resulted in an error. This has been fixed.
You do not need to run DBUpdate after installing this specific upgrade (there have been no database changes), unless you are upgrading from a version prior to 4.22.
