Hi. I am new to Alpha 5 and currently evaluating its possible use for some projects. I have spent some time getting a general familiarity with version 7. I have some immediate questions that I can�t seem to find the answers for, so am hoping someone here can assist.
1) Running the sample applications once the user is positioned within a form the only method for exiting the form seems to be by mouse control. Is there not a default keyboard action for exiting a form?
2) The field tabbing sequence of the examples I have looked at all seem to incorporate automatic cursor repositioning to the first field of the next record after tabbing from the last tab stop in the current record being browsed or edited; meaning that the cursor physically moves to the next record in sequence or into create mode if there is no existing next record. How can this behavior be changed so that the tabbing sequence moves from the last field to the first field of the same record?
3) When creating/entering new records in a table (e.g. the Alpha Sports Invoice Line Items form) is there a way to physically insert new records between existing displayed records? It appears that the only method for adding new records is by appending at the end of the displayed record set.
4) Buttons in the Alpha Sports Invoice Program display a dashed focus outline when tabbed onto. But those outlines are not cleared after the focus moves to the next button via tab. The only way I can clear the outlines is to position the mouse cursor over the affected button or move to another record. It�s hard to figure out where the cursor is planted if the buttons all retain their focus outline once they�ve been tabbed through. Is there some trick to fixing this behavior?
5) File and Record sharing/locking. I can�t find much that addresses specifics of explicit developer control over locks and shares. How can the file access modes (e.g. read/write) and share modes (e.g read/write/none) be controlled or declared? What about record locks, i.e. concurrency controls? I�m particularly concerned about when/how Alpha locks records. Alpha documentation says records are locked when:
a) a user starts changing a record, or entering a new record\
b) the user commits the changes
Which one is it? Also, when linked records are being used how does Alpha handle locking of the main as well as linked record? How does Alpha deal with record locks for parent records when child records that may or may not affect the parent record are being created/edited, as in an invoicing example?
1) Running the sample applications once the user is positioned within a form the only method for exiting the form seems to be by mouse control. Is there not a default keyboard action for exiting a form?
2) The field tabbing sequence of the examples I have looked at all seem to incorporate automatic cursor repositioning to the first field of the next record after tabbing from the last tab stop in the current record being browsed or edited; meaning that the cursor physically moves to the next record in sequence or into create mode if there is no existing next record. How can this behavior be changed so that the tabbing sequence moves from the last field to the first field of the same record?
3) When creating/entering new records in a table (e.g. the Alpha Sports Invoice Line Items form) is there a way to physically insert new records between existing displayed records? It appears that the only method for adding new records is by appending at the end of the displayed record set.
4) Buttons in the Alpha Sports Invoice Program display a dashed focus outline when tabbed onto. But those outlines are not cleared after the focus moves to the next button via tab. The only way I can clear the outlines is to position the mouse cursor over the affected button or move to another record. It�s hard to figure out where the cursor is planted if the buttons all retain their focus outline once they�ve been tabbed through. Is there some trick to fixing this behavior?
5) File and Record sharing/locking. I can�t find much that addresses specifics of explicit developer control over locks and shares. How can the file access modes (e.g. read/write) and share modes (e.g read/write/none) be controlled or declared? What about record locks, i.e. concurrency controls? I�m particularly concerned about when/how Alpha locks records. Alpha documentation says records are locked when:
a) a user starts changing a record, or entering a new record\
b) the user commits the changes
Which one is it? Also, when linked records are being used how does Alpha handle locking of the main as well as linked record? How does Alpha deal with record locks for parent records when child records that may or may not affect the parent record are being created/edited, as in an invoicing example?
Comment