[AccessD] Access 2013 Field Name Capitaliaation

jack drawbridge jackandpat.d at gmail.com
Mon Feb 17 19:36:20 CST 2014


I don't have (nor have never seen 2013) but I've thrown out the question to
a group I participate in. I hope Hans is correct.  Good luck.

If I get anything, I'll post here.


On Mon, Feb 17, 2014 at 8:15 PM, Charlotte Foust
<charlotte.foust at gmail.com>wrote:

> Thanks Jack, but that's just the standard autocorrect in office.  I got a
> lead from an MVP friend (Hans Voeglaar) who suggested that Access has a
> table somewhere that stores names given to fields and doesn't overwrite
> them unless the name changes in some way other than capitalization.  I
> think he's right, because I discovered I can make another change to the
> field name at the same time and the lowercase prefix will stick.
>
> Charlotte
>
>
> On Mon, Feb 17, 2014 at 5:01 PM, jack drawbridge <jackandpat.d at gmail.com
> >wrote:
>
> > Found this via Google (it's Office 2013 specific--includes Access)
> > I don't have 2013 so am unsure if it;s relevant.
> >
> >
> http://office.microsoft.com/en-us/excel-help/automatically-correct-capitalization-HA010354276.aspx
> >
> >
> > On Mon, Feb 17, 2014 at 7:37 PM, Charlotte Foust
> > <charlotte.foust at gmail.com>wrote:
> >
> > > Wise guy!  I'm like a bulldog, I get my teeth into something and won't
> > let
> > > go.  There must be some reason it saves some of the changes but not
> most
> > of
> > > them!  I don't usually name fields like this but on this project I have
> > to
> > > leave as many breadcrumbs and balls of string as possible for the
> > > non-programmers who will maintain it.
> > >
> > > Charlotte
> > >
> > >
> > > On Mon, Feb 17, 2014 at 2:17 PM, John W Colby <jwcolby at gmail.com>
> wrote:
> > >
> > > > Give up and accept that Microsoft knows best?  Mail cat feces to
> > everyone
> > > > at Microsoft?  Follow Arthur to another database product entirely?
> >  Take
> > > up
> > > > Yoga and consider your navel?  Copious quantities of attitude
> enhancing
> > > > drugs?
> > > >
> > > > All of those suggestions are better than shooting yourself.
> > > >
> > > > ;)
> > > >
> > > > John W. Colby
> > > >
> > > > Reality is what refuses to go away
> > > > when you do not believe in it
> > > >
> > > >
> > > > On 2/17/2014 4:57 PM, Charlotte Foust wrote:
> > > >
> > > >> I'm working on my current contract and decided to use lower case
> > > prefixes
> > > >> on field names (Access BE and FE) to indicate table or category of
> the
> > > >> value and insure unique field names.  For some reason, Access keeps
> > > >> recapitalizing the first character of the field names when I save,
> > > close,
> > > >> and reopen the table in design view!  Has anyone else run into this?
> >  I
> > > >> just spent several hours lower casing prefixes only to discover
> after
> > I
> > > >> ran
> > > >> a routine to extract the field names that they had been
> recapitalized!
> > > >>   I've fiddled with turning off Autocorrect, but that seems to do
> > > nothing
> > > >> positive for me.
> > > >>
> > > >> Any suggestions before I try shooting myself?
> > > >>
> > > >> Charlotte
> > > >>
> > > >
> > > > --
> > > > AccessD mailing list
> > > > AccessD at databaseadvisors.com
> > > > http://databaseadvisors.com/mailman/listinfo/accessd
> > > > Website: http://www.databaseadvisors.com
> > > >
> > > --
> > > AccessD mailing list
> > > AccessD at databaseadvisors.com
> > > http://databaseadvisors.com/mailman/listinfo/accessd
> > > Website: http://www.databaseadvisors.com
> > >
> > --
> > AccessD mailing list
> > AccessD at databaseadvisors.com
> > http://databaseadvisors.com/mailman/listinfo/accessd
> > Website: http://www.databaseadvisors.com
> >
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>


More information about the AccessD mailing list