Prev: I'm looking for sample utility billing databases. Master Santo
Next: Text Field Capitalization
From: Steve on 22 Jun 2008 07:16
Hi,
I had a field name with gaps in, created in my early days ! Never any
problem until now.
I have had need to fill the gaps with _ for it to work in an unbound text
box code to pull in a value from another form...and of course gaps are
unacceptable !
I am going through all my forms, records, queries etc as it now upsets them
all. Will take ages ! Is there a quick way of getting access to look for
all occurences of the old field name and alter it to the new one ?
Cheers
Steve


From: bhicks11 via AccessMonster.com on 22 Jun 2008 07:49
Hi Steve,

You can use text with spaces but you must surround with brackets []. I avoid
because it is cleaner and I use VBA a lot.

Bonnie

http://www.dataplus-svc.com


Here's a blurb out of the Access Help:

Names of fields, controls (control: A graphical user interface object, such
as a text box, check box, scroll bar, or command button, that lets users
control the program. You use controls to display data or choices, perform an
action, or make the user interface easier to read.), and objects in Microsoft
Access:

Can be up to 64 characters long.
Can include any combination of letters, numbers, spaces, and special
characters except a period (.), an exclamation point (!), an accent grave (`),
and brackets ([ ]).
Can't begin with leading spaces.
Can't include control characters (ASCII values 0 through 31).
Can't include a double quotation mark (") in table, view, or stored procedure
(stored procedure: A precompiled collection of SQL statements and optional
control-of-flow statements that is stored under a name and processed as a
unit. The collection is stored in an SQL database and can be run with one
call from an application.) names in a Microsoft Access project (Microsoft
Access project: An Access file that connects to a Microsoft SQL Server
database and is used to create client/server applications. A project file
doesn't contain any data or data-definition-based objects such as tables and
views.).
Although you can include spaces in field, control, and object names, most
examples in the Microsoft Access documentation show field and control names
without spaces because spaces in names can produce naming conflicts in
Microsoft Visual Basic for Applications (Visual Basic for Applications (VBA):
A macro-language version of Microsoft Visual Basic that is used to program
Windows applications and is included with several Microsoft applications.) in
some circumstances.

When you name a field, control, or object, it's a good idea to make sure the
name doesn't duplicate the name of a property (property: A named attribute of
a control, a field, or an object that you set to define one of the object's
characteristics (such as size, color, or screen location) or an aspect of its
behavior (such as whether the object is hidden).) or other element used by
Microsoft Access; otherwise, your database can produce unexpected behavior in
some circumstances. For example, if you refer to the value of a field called
Name in a table NameInfo using the syntax NameInfo.Name, Microsoft Access
displays the value of the table's Name property rather than the value of the
Name field.

Another way to avoid unexpected results is to always use the ! operator
instead of the . (dot) operator to refer to the value of a field, control, or
object. For example, the following identifier explicitly refers to the value
of the Name field rather than the Name property:

[NameInfo]![Name]



Steve wrote:
>Hi,
>I had a field name with gaps in, created in my early days ! Never any
>problem until now.
>I have had need to fill the gaps with _ for it to work in an unbound text
>box code to pull in a value from another form...and of course gaps are
>unacceptable !
>I am going through all my forms, records, queries etc as it now upsets them
>all. Will take ages ! Is there a quick way of getting access to look for
>all occurences of the old field name and alter it to the new one ?
>Cheers
>Steve

--
Message posted via http://www.accessmonster.com

From: Steve on 22 Jun 2008 08:15
Hi,
Thats good to know.
However I could do with a way of finding instances of a changed field name
and updating that to the new name across the entire access file as I do find
occurrences of such and all I get is enter parameter value, wish it would
say what I have gone and altered !
I alter a fieldname and need reports and queries and so on to still work,
....dont we all :-)

Steve


"bhicks11 via AccessMonster.com" <u44327(a)uwe> wrote in message
news:860d8494feca8(a)uwe...
> Hi Steve,
>
> You can use text with spaces but you must surround with brackets []. I
> avoid
> because it is cleaner and I use VBA a lot.
>
> Bonnie
>
> http://www.dataplus-svc.com
>
>
> Here's a blurb out of the Access Help:
>
> Names of fields, controls (control: A graphical user interface object,
> such
> as a text box, check box, scroll bar, or command button, that lets users
> control the program. You use controls to display data or choices, perform
> an
> action, or make the user interface easier to read.), and objects in
> Microsoft
> Access:
>
> Can be up to 64 characters long.
> Can include any combination of letters, numbers, spaces, and special
> characters except a period (.), an exclamation point (!), an accent grave
> (`),
> and brackets ([ ]).
> Can't begin with leading spaces.
> Can't include control characters (ASCII values 0 through 31).
> Can't include a double quotation mark (") in table, view, or stored
> procedure
> (stored procedure: A precompiled collection of SQL statements and optional
> control-of-flow statements that is stored under a name and processed as a
> unit. The collection is stored in an SQL database and can be run with one
> call from an application.) names in a Microsoft Access project (Microsoft
> Access project: An Access file that connects to a Microsoft SQL Server
> database and is used to create client/server applications. A project file
> doesn't contain any data or data-definition-based objects such as tables
> and
> views.).
> Although you can include spaces in field, control, and object names, most
> examples in the Microsoft Access documentation show field and control
> names
> without spaces because spaces in names can produce naming conflicts in
> Microsoft Visual Basic for Applications (Visual Basic for Applications
> (VBA):
> A macro-language version of Microsoft Visual Basic that is used to program
> Windows applications and is included with several Microsoft applications.)
> in
> some circumstances.
>
> When you name a field, control, or object, it's a good idea to make sure
> the
> name doesn't duplicate the name of a property (property: A named attribute
> of
> a control, a field, or an object that you set to define one of the
> object's
> characteristics (such as size, color, or screen location) or an aspect of
> its
> behavior (such as whether the object is hidden).) or other element used by
> Microsoft Access; otherwise, your database can produce unexpected behavior
> in
> some circumstances. For example, if you refer to the value of a field
> called
> Name in a table NameInfo using the syntax NameInfo.Name, Microsoft Access
> displays the value of the table's Name property rather than the value of
> the
> Name field.
>
> Another way to avoid unexpected results is to always use the ! operator
> instead of the . (dot) operator to refer to the value of a field, control,
> or
> object. For example, the following identifier explicitly refers to the
> value
> of the Name field rather than the Name property:
>
> [NameInfo]![Name]
>
>
>
> Steve wrote:
>>Hi,
>>I had a field name with gaps in, created in my early days ! Never any
>>problem until now.
>>I have had need to fill the gaps with _ for it to work in an unbound text
>>box code to pull in a value from another form...and of course gaps are
>>unacceptable !
>>I am going through all my forms, records, queries etc as it now upsets
>>them
>>all. Will take ages ! Is there a quick way of getting access to look for
>>all occurences of the old field name and alter it to the new one ?
>>Cheers
>>Steve
>
> --
> Message posted via http://www.accessmonster.com
>


From: Duane Hookom on 22 Jun 2008 09:21
Tony Toews has links to several search and replace utilities on his web page
at http://www.granite.ab.ca/access/thirdparty.htm.
--
Duane Hookom
Microsoft Access MVP


"Steve" wrote:

> Hi,
> Thats good to know.
> However I could do with a way of finding instances of a changed field name
> and updating that to the new name across the entire access file as I do find
> occurrences of such and all I get is enter parameter value, wish it would
> say what I have gone and altered !
> I alter a fieldname and need reports and queries and so on to still work,
> ....dont we all :-)
>
> Steve
>
>
> "bhicks11 via AccessMonster.com" <u44327(a)uwe> wrote in message
> news:860d8494feca8(a)uwe...
> > Hi Steve,
> >
> > You can use text with spaces but you must surround with brackets []. I
> > avoid
> > because it is cleaner and I use VBA a lot.
> >
> > Bonnie
> >
> > http://www.dataplus-svc.com
> >
> >
> > Here's a blurb out of the Access Help:
> >
> > Names of fields, controls (control: A graphical user interface object,
> > such
> > as a text box, check box, scroll bar, or command button, that lets users
> > control the program. You use controls to display data or choices, perform
> > an
> > action, or make the user interface easier to read.), and objects in
> > Microsoft
> > Access:
> >
> > Can be up to 64 characters long.
> > Can include any combination of letters, numbers, spaces, and special
> > characters except a period (.), an exclamation point (!), an accent grave
> > (`),
> > and brackets ([ ]).
> > Can't begin with leading spaces.
> > Can't include control characters (ASCII values 0 through 31).
> > Can't include a double quotation mark (") in table, view, or stored
> > procedure
> > (stored procedure: A precompiled collection of SQL statements and optional
> > control-of-flow statements that is stored under a name and processed as a
> > unit. The collection is stored in an SQL database and can be run with one
> > call from an application.) names in a Microsoft Access project (Microsoft
> > Access project: An Access file that connects to a Microsoft SQL Server
> > database and is used to create client/server applications. A project file
> > doesn't contain any data or data-definition-based objects such as tables
> > and
> > views.).
> > Although you can include spaces in field, control, and object names, most
> > examples in the Microsoft Access documentation show field and control
> > names
> > without spaces because spaces in names can produce naming conflicts in
> > Microsoft Visual Basic for Applications (Visual Basic for Applications
> > (VBA):
> > A macro-language version of Microsoft Visual Basic that is used to program
> > Windows applications and is included with several Microsoft applications.)
> > in
> > some circumstances.
> >
> > When you name a field, control, or object, it's a good idea to make sure
> > the
> > name doesn't duplicate the name of a property (property: A named attribute
> > of
> > a control, a field, or an object that you set to define one of the
> > object's
> > characteristics (such as size, color, or screen location) or an aspect of
> > its
> > behavior (such as whether the object is hidden).) or other element used by
> > Microsoft Access; otherwise, your database can produce unexpected behavior
> > in
> > some circumstances. For example, if you refer to the value of a field
> > called
> > Name in a table NameInfo using the syntax NameInfo.Name, Microsoft Access
> > displays the value of the table's Name property rather than the value of
> > the
> > Name field.
> >
> > Another way to avoid unexpected results is to always use the ! operator
> > instead of the . (dot) operator to refer to the value of a field, control,
> > or
> > object. For example, the following identifier explicitly refers to the
> > value
> > of the Name field rather than the Name property:
> >
> > [NameInfo]![Name]
> >
> >
> >
> > Steve wrote:
> >>Hi,
> >>I had a field name with gaps in, created in my early days ! Never any
> >>problem until now.
> >>I have had need to fill the gaps with _ for it to work in an unbound text
> >>box code to pull in a value from another form...and of course gaps are
> >>unacceptable !
> >>I am going through all my forms, records, queries etc as it now upsets
> >>them
> >>all. Will take ages ! Is there a quick way of getting access to look for
> >>all occurences of the old field name and alter it to the new one ?
> >>Cheers
> >>Steve
> >
> > --
> > Message posted via http://www.accessmonster.com
> >
>
>
>
From: Klatuu on 23 Jun 2008 09:57
Here is a link to a favorite of mine:
http://www.rickworld.com/download.html


--
Dave Hargis, Microsoft Access MVP


"Steve" wrote:

> Hi,
> Thats good to know.
> However I could do with a way of finding instances of a changed field name
> and updating that to the new name across the entire access file as I do find
> occurrences of such and all I get is enter parameter value, wish it would
> say what I have gone and altered !
> I alter a fieldname and need reports and queries and so on to still work,
> ....dont we all :-)
>
> Steve
>
>
> "bhicks11 via AccessMonster.com" <u44327(a)uwe> wrote in message
> news:860d8494feca8(a)uwe...
> > Hi Steve,
> >
> > You can use text with spaces but you must surround with brackets []. I
> > avoid
> > because it is cleaner and I use VBA a lot.
> >
> > Bonnie
> >
> > http://www.dataplus-svc.com
> >
> >
> > Here's a blurb out of the Access Help:
> >
> > Names of fields, controls (control: A graphical user interface object,
> > such
> > as a text box, check box, scroll bar, or command button, that lets users
> > control the program. You use controls to display data or choices, perform
> > an
> > action, or make the user interface easier to read.), and objects in
> > Microsoft
> > Access:
> >
> > Can be up to 64 characters long.
> > Can include any combination of letters, numbers, spaces, and special
> > characters except a period (.), an exclamation point (!), an accent grave
> > (`),
> > and brackets ([ ]).
> > Can't begin with leading spaces.
> > Can't include control characters (ASCII values 0 through 31).
> > Can't include a double quotation mark (") in table, view, or stored
> > procedure
> > (stored procedure: A precompiled collection of SQL statements and optional
> > control-of-flow statements that is stored under a name and processed as a
> > unit. The collection is stored in an SQL database and can be run with one
> > call from an application.) names in a Microsoft Access project (Microsoft
> > Access project: An Access file that connects to a Microsoft SQL Server
> > database and is used to create client/server applications. A project file
> > doesn't contain any data or data-definition-based objects such as tables
> > and
> > views.).
> > Although you can include spaces in field, control, and object names, most
> > examples in the Microsoft Access documentation show field and control
> > names
> > without spaces because spaces in names can produce naming conflicts in
> > Microsoft Visual Basic for Applications (Visual Basic for Applications
> > (VBA):
> > A macro-language version of Microsoft Visual Basic that is used to program
> > Windows applications and is included with several Microsoft applications.)
> > in
> > some circumstances.
> >
> > When you name a field, control, or object, it's a good idea to make sure
> > the
> > name doesn't duplicate the name of a property (property: A named attribute
> > of
> > a control, a field, or an object that you set to define one of the
> > object's
> > characteristics (such as size, color, or screen location) or an aspect of
> > its
> > behavior (such as whether the object is hidden).) or other element used by
> > Microsoft Access; otherwise, your database can produce unexpected behavior
> > in
> > some circumstances. For example, if you refer to the value of a field
> > called
> > Name in a table NameInfo using the syntax NameInfo.Name, Microsoft Access
> > displays the value of the table's Name property rather than the value of
> > the
> > Name field.
> >
> > Another way to avoid unexpected results is to always use the ! operator
> > instead of the . (dot) operator to refer to the value of a field, control,
> > or
> > object. For example, the following identifier explicitly refers to the
> > value
> > of the Name field rather than the Name property:
> >
> > [NameInfo]![Name]
> >
> >
> >
> > Steve wrote:
> >>Hi,
> >>I had a field name with gaps in, created in my early days ! Never any
> >>problem until now.
> >>I have had need to fill the gaps with _ for it to work in an unbound text
> >>box code to pull in a value from another form...and of course gaps are
> >>unacceptable !
> >>I am going through all my forms, records, queries etc as it now upsets
> >>them
> >>all. Will take ages ! Is there a quick way of getting access to look for
> >>all occurences of the old field name and alter it to the new one ?
> >>Cheers
> >>Steve
> >
> > --
> > Message posted via http://www.accessmonster.com
> >
>
>
>
 |  Next  |  Last
Pages: 1 2
Prev: I'm looking for sample utility billing databases. Master Santo
Next: Text Field Capitalization