Brackets in formulae

[Stephen Haley]

I have a field on a form whose source is pointed at a subform textbox.
When I originally created the form access was quite happy with the
expression
=SFActionPlan_SFObj.Form!ObjectiveID
but now it insists on putting brackets arround everything
=[SFActionPlan_SFObj].[Form]![ObjectiveID]

I know there appears to be little diff but was wondering what caused the
change in behavior and if it is something to worry about. The formula
[cmbGeoID].[column](3)
when refering to the 3rd col in a dropbox just looks wrong to me but appears
to work.

rgds
stephen

 

[Br@dley]

I have a field on a form whose source is pointed at a subform textbox.
When I originally created the form access was quite happy with the
expression
=SFActionPlan_SFObj.Form!ObjectiveID
but now it insists on putting brackets arround everything
=[SFActionPlan_SFObj].[Form]![ObjectiveID]

I know there appears to be little diff but was wondering what caused
the change in behavior and if it is something to worry about. The
formula [cmbGeoID].[column](3)
when refering to the 3rd col in a dropbox just looks wrong to me but
appears to work.

rgds
stephen

It's fine. Brackets are needed if you have spaces in the object name
(and IMO it's good practice to put brackets around things anyway.. but
other's disagree. Access will tend to put brackets in when entering in
things into the property sheet (and probably other places too).
--
regards,

Bradley

A Christian Response
http://www.pastornet.net.au/response

 

[Stephen Haley]

I was more curious about the sudden change in behavior - it didnt use to do
it but now it does..
ie if I go in and edit old fields that didnt have brackets it now insists on
putting them in..
rgds
stephen

I have a field on a form whose source is pointed at a subform textbox.
When I originally created the form access was quite happy with the
expression
=SFActionPlan_SFObj.Form!ObjectiveID
but now it insists on putting brackets arround everything
=[SFActionPlan_SFObj].[Form]![ObjectiveID]

I know there appears to be little diff but was wondering what caused
the change in behavior and if it is something to worry about. The
formula [cmbGeoID].[column](3)
when refering to the 3rd col in a dropbox just looks wrong to me but
appears to work.

rgds
stephen

It's fine. Brackets are needed if you have spaces in the object name (and
IMO it's good practice to put brackets around things anyway.. but other's
disagree. Access will tend to put brackets in when entering in things
into the property sheet (and probably other places too).
--
regards,

Bradley

A Christian Response
http://www.pastornet.net.au/response