Hello!
I previously had tried A5 v1.02 and found that, while nice, it lacked some features. After the message board members assured me that the more recent versions were a big improvement, I purchased a copy a copy of A5 v3.04b.
I realize that it doesn't have all of A5 v4.03 features, but I wanted to know if it was worth it to move to the latest version of A5.
While I have found that A5 v3.04b has many improvements over v1.02, I've stumbled across some bugs/problems with v3.04b and was wondering if they had been resolved in the current v4.03. Since v3.04b was the final version of 3, I thought it would be (relatively) bug-free.
The first problem that I encountered is when deleting records in a one-to-many form using an embedded browse. I created a one-to-many form using the invoice set in the sample invoice database provided with v3.04b. I've noticed that on an occasional basis, deleting the last invoice in the set would cause the preceding records to disappear.
For example, if I had entered invoice #'s 1-5 and then deleted #5, #'s 1-4 would also disappear! Browsing the individual invoice header and detail tables separately showed that the records still existed and were not marked or deleted. But in viewing the tables as a set, they were gone. I found that the only way to recover them was to pack the set, and the records (invoice #'s 1-4) would reappear!
The readme file for v3.04b mentioned a problem when browsing and deleting records in a set, but I was using a form and the problem seemed to be different from that described in the readme.
I encountered another problem with the one-to-many invoice set and the form with an embedded browse. I placed a delete button on the form using the button genie. This button executes the inline Xbasic method "topparent.delete_record()". I found that most of the time, the delete button would delete the parent record and the related child records as expected. Pressing ^DEL deleted individual child records. However, I noticed pressing the Delete button while a child record had focus occasionally resulted in only the one highlighted child record being deleted. (At first I thought it was just my imagination, but I found that it recurred.)
My final concern is that I found the form designer to be awkward to deal with. I know that many A5 users on this board have praised the ease and power of the form designer, but I find it a bit difficult compared to others, such as Paradox. (And, yes, I know how many board members feel that Paradox is difficult!)
Now I realize that v3.04b is history, but my concern and question is whether problems such as these have been corrected in v4.03 or the upcoming v5.0. I've read reports of unsolved problems such as heap lock failures (and, yes,I've seen Dr. Wayne's recent article) amongst others and am wondering if A5 v4.03 and the upcoming v5.0 will cure the frustrating problems that I experienced with v3.04b?
Any input will be appreciated.
O.J.
I previously had tried A5 v1.02 and found that, while nice, it lacked some features. After the message board members assured me that the more recent versions were a big improvement, I purchased a copy a copy of A5 v3.04b.
I realize that it doesn't have all of A5 v4.03 features, but I wanted to know if it was worth it to move to the latest version of A5.
While I have found that A5 v3.04b has many improvements over v1.02, I've stumbled across some bugs/problems with v3.04b and was wondering if they had been resolved in the current v4.03. Since v3.04b was the final version of 3, I thought it would be (relatively) bug-free.
The first problem that I encountered is when deleting records in a one-to-many form using an embedded browse. I created a one-to-many form using the invoice set in the sample invoice database provided with v3.04b. I've noticed that on an occasional basis, deleting the last invoice in the set would cause the preceding records to disappear.
For example, if I had entered invoice #'s 1-5 and then deleted #5, #'s 1-4 would also disappear! Browsing the individual invoice header and detail tables separately showed that the records still existed and were not marked or deleted. But in viewing the tables as a set, they were gone. I found that the only way to recover them was to pack the set, and the records (invoice #'s 1-4) would reappear!
The readme file for v3.04b mentioned a problem when browsing and deleting records in a set, but I was using a form and the problem seemed to be different from that described in the readme.
I encountered another problem with the one-to-many invoice set and the form with an embedded browse. I placed a delete button on the form using the button genie. This button executes the inline Xbasic method "topparent.delete_record()". I found that most of the time, the delete button would delete the parent record and the related child records as expected. Pressing ^DEL deleted individual child records. However, I noticed pressing the Delete button while a child record had focus occasionally resulted in only the one highlighted child record being deleted. (At first I thought it was just my imagination, but I found that it recurred.)
My final concern is that I found the form designer to be awkward to deal with. I know that many A5 users on this board have praised the ease and power of the form designer, but I find it a bit difficult compared to others, such as Paradox. (And, yes, I know how many board members feel that Paradox is difficult!)
Now I realize that v3.04b is history, but my concern and question is whether problems such as these have been corrected in v4.03 or the upcoming v5.0. I've read reports of unsolved problems such as heap lock failures (and, yes,I've seen Dr. Wayne's recent article) amongst others and am wondering if A5 v4.03 and the upcoming v5.0 will cure the frustrating problems that I experienced with v3.04b?
Any input will be appreciated.
O.J.