07 vs 2003 properties

[autoIT]

in 2007 upper case is coded as

Ucase(Name)

I'm getting an error in 2003. What is the difference?

Adam

 

[Remou]

Is Name the name of the field? Name is a reserved word.

 

[autoIT]

correction

UCase(txtEmpQry.Text)

for example

 

[PHV]

Perhaps this ?
UCase(txtEmpQry.Value)

Anyway, why not posting the error message ????

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

 

[autoIT]

can't find project or library and it stops at a Ucase

what library works best with 2003??

Adam

 

[Remou]

Have you checked your references to see if any are marked 'MISSING'? Have you tried UCase in a fresh database? What about StrConv, does that work?

 

[Ed2020]

If memory serves UCase lives in the VBA library, so it shouldn't be possible for this to be missing.

I've seen similar problems under 2003 with the Environ function. I believe a reinstallation of Office was needed to fix that issue.

Ed Metcalfe.

Please do not feed the trolls.....

 

[autoIT]

Remou,

Which references should be present. Up until now I've been usin access 07 beta with refernce library 2.8. I saved the db with an .mdb extension moved it to the server and when I attempt to open it with 2003 part of it works, and some of it doesn't saying a reerence lib is missing. I have ref lib 2.0-2.8 which one would be best to use in this case? It's not too completed, your basic if statements do loops, ucase properties, .visibles, etc. I never new which reference libraries neede to be checked off, i always just went with the flow.


Adam

 

[Remou]

As Ed2020 says, UCase lives in the Visual Basic for Applications Library, which does not have a number. Microsoft Access 7.0 Beta has a Microsoft Access 12.0 Object Library (2003 is 11.0, I think), so which library is 2.8? ADO, DAO?