Often times, we spend so much time posting and reposting on this site, when just a few minutes on the telephone would be so helpful. I would put that on your improvement list... some sort of hotline that could be used at certain times. I realize this is tough since you do not have a dedicated call center. Worse yet, it costs money. I realize that this forum is an excellent resource, but we all seem to encounter our unique little dilemmas that this forum cannot fix. Often times, time is of the essence, and we desperately want to get the problem resolved so that we can move on to more important issues that need to be addressed while we are home. I have used the APDL on and off for nearly two years. It is a good concept and has many potentially beneficial features, however; I felt like a participant in a beta test for these past two years. While I am happy to contribute to the improvement of the product, it is frustrating when it is potentially corrupting my flight time data. The issue I have had to ask myself time and again is, "Can I trust this program to track my data?" I haven't always felt confident, and for that reason, have resorted to my old crew log from time to time. When a new update presents itself, I try to go back to using the APDL. The recent PPC update seems to be doing pretty good, although I haven't retested some of my previous problems yet. Perhaps you could provide a specific update. Were the following issues ever corrected:
- Required rest page... sometimes information from the previous night was not being included in the 24 hour calculation for rest purposes... in other words, a series of flights may have completed around 22:30 on day#1, and a new series began around 11:00am on day#2. Even thought all these flights should be considered in the day#2 required rest calculation, the day#2 info. is the only info. considered, and day#1 times are replaced with "no activity". I think Paul said this was due to flights that end after midnight zulu or domicile time... can't remember exactly. For whatever reason, the times got dumped out of the req. rest calculation. Any update on this error... was it repaired?
- Syncing with logbook pro... I fly both the Embraer 145 and 135 aircraft. When I enter a/c data into APDL, I enter the N# and then the a/c type, E145 or E135. When I sync to logbook pro, the sync software asks for a default a/c type, to which I provide E145. PROBLEM: When the data is input to logbook pro, all a/c types go in as E145, even if some of my APDL flight entries are E135. Can't the programs delineate between the two based on the N#'s and enter the appropriate a/c type so that I do not have to go back and manually change line entries in logbook pro? The autosync is kinda pointless if I have to go back and manually repair the information.
- The pay features are a great try at tracking the complex pay issues of the airline environment. Unfortunately, I cannot use them b/c our damn contracts are so full of legalese and complexities, that no program could ever hope to tackle all these issues. Thanks for trying though. The basics are there.