Control Source "=[firstname] & " " & [surname]" = #E

[idbr]

Any ideas why this should be? Both fields exist and are in the form's recordset.

I can't perform any other operations such as Left(), Right() etc either!

Bit confused really...

Thanks, Iain

(running A2000 on win2000)

 

[idbr]

The title should end =#Error btw, damn length limits

 

[PHV]

I can't perform any other operations such as Left(), Right()
double check the references:
when in VBE menu Tools -> References ...

You may also verify that the DB compiles properly:
menu Debug -> Compiles ...

Hope This Helps, PH.
Want to get great answers to your Tek-Tips questions? Have a look at FAQ219-2884 or FAQ181-2886

 

[idbr]

Sorry PHV, just in this control, not in the entire db. Also, just on a subform - which I should have metioned apologies.

 

[Eupher]

Hi, idbr,

Are there quote marks surrounding the entire expression, just as you posted in your subject line? If so, remove them...

Ken S.

 

[JoeAtWork]

This is what you should have in the Control Source property:

=[firstname] & " " & [surname]

Any field names or functions like Left(), Right(), should be outside of the quotes.

 

[idbr]

Gents, the quotes were just for clarity in the title.

Thanks, Iain

 

[JoeAtWork]

Gents, the quotes were just for clarity in the title.

Had the opposite effect.

 

[idbr]

Hey, call it a methodology... ;-)

 

[TheAceMan1]

How are ya idbr . . .

Under the circumstances I'd [blue]delete & reconstitute the control.[/blue]

Before you do does a simple [blue][tt]="Test"[/tt][/blue] work?

See Ya! . . . . . .

 

[idbr]

Have tried that AceMan, didn't do the job I'm afraid. "Test" does work, as does binding the control to a field. It's just when I try to make it a calculated control, by whatever means, that it doesn't work. But just on the subform, not on the main form itself.

Weird... %-)

 

[TheAceMan1]

idbr . . .

Is the [blue]Name[/blue] property for the [blue]FirstName & SurName[/blue] fields the same?

See Ya! . . . . . .

 

[idbr]

All,

Have figured it out. Not a syntax problem, rather a micro$oft one. Needed to install SP3 for Office, this fixes the bug.

Nothing in the knowledge base though, unusual.

Thanks, Iain