generally in something like that, the first is the list of available objects to select, the second is the selected tables.
generally single arrow keys are for moving one object, doubles are for moving all objects.
wizards in access have never been done well, I think its a major trouble getting jaws to work with the wizard interface.
HTH, elf proprietor, The Grab Bag, for blind computer users and programmers http://grabbag.alacorncomputer.com Owner: Alacorn Computer Enterprises "own the might and majesty of a Alacorn!" www.alacorncomputer.com----- Original Message ----- From: "DaShiell, Jude T. CIV NAVAIR 1490, 1, 26" <jude.dashiell@xxxxxxxx>
To: <programmingblind@xxxxxxxxxxxxx> Sent: Monday, September 28, 2009 11:59 AM Subject: Msaccess2000 upsizing wizard and jaws 8.x My speculation now is that there's a real mouse trap in the upsizing wizard that appears on the tables selection screen and prevents selecting any more than a single table to send over to sql. When the msaccess script was written it was also probably only tested with a single table database. That or the script writers couldn't figure a work around for the mouse trap. All kinds of unlabeled buttons with single and double left and right arrows and what appear to be two parallel lists. First list shows tables and second list is empty. What I have now has 10 tables all connected by autonumber fields. I can probably get those auto number fields converted to numeric but doubt that will solve the rest of this problem. Jaws mouse keys don't appear to work on that screen either. Best solution will likely end up being to have someone not using accessibility software convert the database then I'll do the remaining work in the project. Rot47: <;F56]52D9:6==@?2GJ]>:=> __________ View the list's information and change your settings at //www.freelists.org/list/programmingblind __________View the list's information and change your settings at //www.freelists.org/list/programmingblind