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 andDate:
Fri, Jan 6, 2012 1:54:30 pmThis is a multi-part message in MIME format.
--------------050004020208060205030104
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
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
> *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.
--------------050004020208060205030104
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">
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.<br>
<br>
On 1/6/2012 1:45 PM, Katherine Moss wrote:
<blockquote
cite="mid:6C2EC6FBAFC68E4F9694F1BD2BA5BC7D2323389A@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><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
color:black;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";
color:black;}
span.EmailStyle17
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;
color:black;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
..MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div class="WordSection1">
<p class="MsoNormal"><span style="color:#1F497D">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></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF
1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span
style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext">From:</span></b><span
style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext">
Aaron Smith [<a class="moz-txt-link-freetext" href="mailto:aaron@gwmicro.com">mailto:aaron@gwmicro.com</a>]
<br>
<b>Sent:</b> Friday, January 06, 2012 12:08 PM<br>
<b>Cc:</b> <a class="moz-txt-link-abbreviated" href="mailto:gw-apps@gwmicro.com">gw-apps@gwmicro.com</a><br>
<b>Subject:</b> Re: MS Access and WE problems (noticed
when typing in fields and when designing)<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">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: <o:p></o:p></p>
<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>
<p class="MsoNormal"><span
style="font-size:12.0pt;font-family:"Times New
Roman","serif""><br>
<br>
<o:p></o:p></span></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>
</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>
--------------050004020208060205030104--
--------------050004020208060205030104
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
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
> *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.
--------------050004020208060205030104
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">
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.<br>
<br>
On 1/6/2012 1:45 PM, Katherine Moss wrote:
<blockquote
cite="mid:6C2EC6FBAFC68E4F9694F1BD2BA5BC7D2323389A@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><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
color:black;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";
color:black;}
span.EmailStyle17
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;
color:black;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
..MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div class="WordSection1">
<p class="MsoNormal"><span style="color:#1F497D">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></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF
1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span
style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext">From:</span></b><span
style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext">
Aaron Smith [<a class="moz-txt-link-freetext" href="mailto:aaron@gwmicro.com">mailto:aaron@gwmicro.com</a>]
<br>
<b>Sent:</b> Friday, January 06, 2012 12:08 PM<br>
<b>Cc:</b> <a class="moz-txt-link-abbreviated" href="mailto:gw-apps@gwmicro.com">gw-apps@gwmicro.com</a><br>
<b>Subject:</b> Re: MS Access and WE problems (noticed
when typing in fields and when designing)<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">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: <o:p></o:p></p>
<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>
<p class="MsoNormal"><span
style="font-size:12.0pt;font-family:"Times New
Roman","serif""><br>
<br>
<o:p></o:p></span></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>
</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>
--------------050004020208060205030104--
