GW Micro - Support - Email List Archives

The GW-Apps is geared toward discussions of Window-Eyes and GW Micro apps. Any subscriber of the GW-Apps list has the ability to post on-topic messages.

From:

Aaron Smith <aaron@gwmicro.com>

Subject:

Re: MS Access and WE problems (noticed when typing in fields and

Date:

Fri, Jan 6, 2012 12:08:07 pm

This is a multi-part message in MIME format.
--------------050408090609010105050301
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Beefing up Access support in the Access app is on our list. Right now,
Access 2003 is working best, followed by Access 2007, followed by Access
2010. We'll be focusing on 2007 and 2010 in the next app update.

Aaron

On 1/6/2012 12:40 AM, Katherine Moss wrote:
>
> Hello all,
>
> Not that I am a whiz at MS Access 2010 (I'm just learning it), but in
> my learning, or attempts thereof, I have discovered some real issues
> with Access and WE. For one thing, when in design view, WE does not
> speak very well which field you are on, and I can just get it to
> sometimes speak the data types when setting up the database, but once
> you get out of there, you can't tell which field you are on anyway, so
> trying to design them seemed to have served no purpose in the first
> place. And then once you get out of design view and you try to type
> into one of the fields (and after praying to the Lord that you are on
> the right one), you're lucky if you get a correct placement. Is this
> something really simple on my end that I'm missing? Or more directly,
> how would you suggest that a Window-Eyes user use Access 2010? And I
> have the latest version of the MS Access app installed as well, so
> that's why this question is going on this list to begin with, but if
> it should be moved, you can move it. Thanks folks.
>
> Katherine Moss,
>
> Administrator of the AccessCop Network, previously Raeder24.org.
> Visit us on the web at http://raeder24.org <http://raeder24.org/>;
>

--
Aaron Smith
Web Development * App Development * Product Support Specialist
GW Micro, Inc. * 725 Airport North Office Park, Fort Wayne, IN 46825
260-489-3671 * gwmicro.com

To insure that you receive proper support, please include all past
correspondence (where applicable), and any relevant information
pertinent to your situation when submitting a problem report to the GW
Micro Technical Support Team.

--------------050408090609010105050301
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Beefing up Access support in the Access app is on our list. Right
now, Access 2003 is working best, followed by Access 2007, followed
by Access 2010. We'll be focusing on 2007 and 2010 in the next app
update.<br>
<br>
Aaron<br>
<br>
On 1/6/2012 12:40 AM, Katherine Moss wrote:
<blockquote
cite="mid:6C2EC6FBAFC68E4F9694F1BD2BA5BC7D232327CF@SN2PRD0102MB129.prod.exchangelabs.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
<meta name="Generator" content="Microsoft Word 14 (filtered
medium)">
<style></style>
<div class="WordSection1">
<p class="MsoNormal">Hello all,<o:p></o:p></p>
<p class="MsoNormal">Not that I am a whiz at MS Access 2010 (I’m
just learning it), but in my learning, or attempts thereof, I
have discovered some real issues with Access and WE.  For one
thing, when in design view, WE does not speak very well which
field you are on, and I can just get it to sometimes speak the
data types when setting up the database, but once you get out
of there, you can’t tell which field you are on anyway, so
trying to design them seemed to have served no purpose in the
first place.  And then once you get out of design view and you
try to type into one of the fields (and after praying to the
Lord that you are on the right one), you’re lucky if you get a
correct placement.  Is this something really simple on my end
that I’m missing?  Or more directly, how would you suggest
that a Window-Eyes user use Access 2010?  And I have the
latest version of the MS Access app installed as well, so
that’s why this question is going on this list to begin with,
but if it should be moved, you can move it.  Thanks folks.  <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Katherine Moss,<o:p></o:p></p>
<p class="MsoNormal">Administrator of the AccessCop Network,
previously Raeder24.org.  Visit us on the web at
<a moz-do-not-send="true" href="http://raeder24.org/">http://raeder24.org</a><o:p></o:p></p>;
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Aaron Smith
Web Development * App Development * Product Support Specialist
GW Micro, Inc. * 725 Airport North Office Park, Fort Wayne, IN 46825
260-489-3671 * gwmicro.com

To insure that you receive proper support, please include all past
correspondence (where applicable), and any relevant information
pertinent to your situation when submitting a problem report to the GW
Micro Technical Support Team.</pre>
</body>
</html>

--------------050408090609010105050301--