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:

Katherine Moss <Katherine.Moss@gordon.edu>

Subject:

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

Date:

Fri, Jan 6, 2012 2:18:19 pm

--_000_6C2EC6FBAFC68E4F9694F1BD2BA5BC7D23233A0ASN2PRD0102MB129_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Ah okay. I'll have to tell my mentors that then because I may need an additional set of eyes.

From: Aaron Smith [mailto:aaron@gwmicro.com]
Sent: Friday, January 06, 2012 2:11 PM
To: gw-apps@gwmicro.com
Subject: Re: MS Access and WE problems (noticed when typing in fields and when designing)

Form view should certainly work. Design or table view, however, will read cell contents, but not cell headers. That's what we need to work on.

Aaron

On 1/6/2012 2:05 PM, Katherine Moss wrote:
Oh haha that makes sense. So does Access 2010 work at all right now? I ask because I'm doing a project at my college with my mentors there and it's kind of required for the scenario I'm trying to use.

From: Aaron Smith [mailto:aaron@gwmicro.com]
Sent: Friday, January 06, 2012 1:54 PM
To: gw-apps@gwmicro.com<mailto:gw-apps@gwmicro.com>
Subject: Re: MS Access and WE problems (noticed when typing in fields and when designing)

That's a good question, and for the most part, Microsoft did make Access 2010 more accessible than 2003 (which is why the app currently puts more emphasis on the earlier version). But the biggest reason that we put more effort into getting Access 2003 working is because that is the version that was used by the people who first came to us and said, "Please make this database I'm using work better." Now that 2007 and 2010 users are becoming more prolific, we'll start putting more resources into working with those version.

On 1/6/2012 1:45 PM, Katherine Moss wrote:
Okay then, so what support of Access 2010 is currently offered? And shouldn't support of the different versions go the other way around? In that the latest version out there should come first? Just curious. Thanks for updating us though.

From: Aaron Smith [mailto:aaron@gwmicro.com]
Sent: Friday, January 06, 2012 12:08 PM
Cc: gw-apps@gwmicro.com<mailto:gw-apps@gwmicro.com>
Subject: Re: MS Access and WE problems (noticed when typing in fields and when designing)

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.

--

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.

--

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.

--_000_6C2EC6FBAFC68E4F9694F1BD2BA5BC7D23233A0ASN2PRD0102MB129_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml"; xmlns="http://www.w3.org/TR/REC-html40">;
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<style></style>
</head>
<body bgcolor="white" lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
Ah okay.  I’ll have to tell my mentors that then because I may need an additional set of eyes. 
<o:p></o:p>
<o:p> </o:p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
From: Aaron Smith [mailto:aaron@gwmicro.com]
 
Sent: Friday, January 06, 2012 2:11 PM 
To: gw-apps@gwmicro.com 
Subject: Re: MS Access and WE problems (noticed when typing in fields and when designing)<o:p></o:p>
</div>
</div>
<o:p> </o:p>
Form view should certainly work. Design or table view, however, will read cell contents, but not cell headers. That's what we need to work on. 
 
Aaron 
 
On 1/6/2012 2:05 PM, Katherine Moss wrote: <o:p></o:p>
Oh haha that makes sense.  So does Access 2010 work at all right now?  I ask because I’m doing a project at my college with my mentors there and it’s kind of required for the scenario I’m trying to use. 
<o:p></o:p>
 <o:p></o:p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
From: Aaron Smith [<a href="mailto:aaron@gwmicro.com">mailto:aaron@gwmicro.com</a>]
 
Sent: Friday, January 06, 2012 1:54 PM 
To: <a href="mailto:gw-apps@gwmicro.com">gw-apps@gwmicro.com</a> 
Subject: Re: MS Access and WE problems (noticed when typing in fields and when designing)<o:p></o:p>
</div>
</div>
 <o:p></o:p>
That's a good question, and for the most part, Microsoft did make Access 2010 more accessible than 2003 (which is why the app currently puts more emphasis on the earlier version). But the biggest reason that we put more effort into getting
Access 2003 working is because that is the version that was used by the people who first came to us and said, "Please make this database I'm using work better." Now that 2007 and 2010 users are becoming more prolific, we'll start putting more resources into
working with those version. 
 
On 1/6/2012 1:45 PM, Katherine Moss wrote: <o:p></o:p>
Okay then, so what support of Access 2010 is currently offered?  And shouldn’t support of the different versions go the other way around?  In that the latest version out there should come first?  Just curious. 
Thanks for updating us though.  <o:p></o:p>
 <o:p></o:p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
From: Aaron Smith [<a href="mailto:aaron@gwmicro.com">mailto:aaron@gwmicro.com</a>]
 
Sent: Friday, January 06, 2012 12:08 PM 
Cc: <a href="mailto:gw-apps@gwmicro.com">gw-apps@gwmicro.com</a> 
Subject: Re: MS Access and WE problems (noticed when typing in fields and when designing)<o:p></o:p>
</div>
</div>
 <o:p></o:p>
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: <o:p></o:p>
Hello all,<o:p></o:p>
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>
 <o:p></o:p>
Katherine Moss,<o:p></o:p>
Administrator of the AccessCop Network, previously Raeder24.org.  Visit us on the web at
<a href="http://raeder24.org/">http://raeder24.org</a><o:p></o:p>;
 <o:p></o:p>
 
 
 
 
<o:p></o:p>
<pre>-- <o:p></o:p></pre>
<pre>Aaron Smith <o:p></o:p></pre>
<pre>Web Development * App Development * Product Support Specialist<o:p></o:p></pre>
<pre>GW Micro, Inc. * 725 Airport North Office Park, Fort Wayne, IN 46825<o:p></o:p></pre>
<pre>260-489-3671 * gwmicro.com<o:p></o:p></pre>
<pre> <o:p></o:p></pre>
<pre>To insure that you receive proper support, please include all past<o:p></o:p></pre>
<pre>correspondence (where applicable), and any relevant information<o:p></o:p></pre>
<pre>pertinent to your situation when submitting a problem report to the GW<o:p></o:p></pre>
<pre>Micro Technical Support Team.<o:p></o:p></pre>
 
 
 
<o:p></o:p>
<pre>-- <o:p></o:p></pre>
<pre>Aaron Smith <o:p></o:p></pre>
<pre>Web Development * App Development * Product Support Specialist<o:p></o:p></pre>
<pre>GW Micro, Inc. * 725 Airport North Office Park, Fort Wayne, IN 46825<o:p></o:p></pre>
<pre>260-489-3671 * gwmicro.com<o:p></o:p></pre>
<pre> <o:p></o:p></pre>
<pre>To insure that you receive proper support, please include all past<o:p></o:p></pre>
<pre>correspondence (where applicable), and any relevant information<o:p></o:p></pre>
<pre>pertinent to your situation when submitting a problem report to the GW<o:p></o:p></pre>
<pre>Micro Technical Support Team.<o:p></o:p></pre>
 
 
<o:p></o:p>
<pre>-- <o:p></o:p></pre>
<pre>Aaron Smith <o:p></o:p></pre>
<pre>Web Development * App Development * Product Support Specialist<o:p></o:p></pre>
<pre>GW Micro, Inc. * 725 Airport North Office Park, Fort Wayne, IN 46825<o:p></o:p></pre>
<pre>260-489-3671 * gwmicro.com<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>To insure that you receive proper support, please include all past<o:p></o:p></pre>
<pre>correspondence (where applicable), and any relevant information<o:p></o:p></pre>
<pre>pertinent to your situation when submitting a problem report to the GW<o:p></o:p></pre>
<pre>Micro Technical Support Team.<o:p></o:p></pre>
</div>
</body>
</html>

--_000_6C2EC6FBAFC68E4F9694F1BD2BA5BC7D23233A0ASN2PRD0102MB129_--