jwperez
09-16-2004, 05:41 PM
We had just migrated one of our PowerBuilder applications (a graduate student management system) from version 3.x to version 9.0 with no problems at all — except for the fact that on a lookup window (in which the user keys in a student ID number & clicks a button to retrieve records), the cursor gets positioned differently on all subsequent calls to that window than it does on the first call. The data window which holds the user input has an ssn-style edit mask, none of which changed in the migration. In fact, the only difference at all between the previous version and the current version is that the caption says "student ID" instead of "ssn" — no other code changed on that object.
What's supposed to happen is this: The user logs in & goes to the main window of the application. The user clicks on a search button which pops up the window we're talking about. The field already has dashes in it and the cursor is blinking in the left-most position, ready for the user to start typing. As the user keys in the student ID, the object knows to "jump over" the dashes. The user clicks retrieve & gets another window with the desired student record. The search window remains in the background. When finished, if the user has more records to work on, they'll click a cancel button to close the student record screen & do another search.
Here's where the problem comes in. Before the migration, the cursor would still be in the left-most position & the field blanked out. Now, after the migration, the field is still blanked out, but the cursor is now in the RIGHT-most position, making the user backspace 9 times to get to where they need to be to key in the next student ID to search on. Any advice on resolving this problem would be greatly appreciated.
What's supposed to happen is this: The user logs in & goes to the main window of the application. The user clicks on a search button which pops up the window we're talking about. The field already has dashes in it and the cursor is blinking in the left-most position, ready for the user to start typing. As the user keys in the student ID, the object knows to "jump over" the dashes. The user clicks retrieve & gets another window with the desired student record. The search window remains in the background. When finished, if the user has more records to work on, they'll click a cancel button to close the student record screen & do another search.
Here's where the problem comes in. Before the migration, the cursor would still be in the left-most position & the field blanked out. Now, after the migration, the field is still blanked out, but the cursor is now in the RIGHT-most position, making the user backspace 9 times to get to where they need to be to key in the next student ID to search on. Any advice on resolving this problem would be greatly appreciated.