Lcase
- Thread starter kitty77
- Start date
Isaac
Lifelong Learner
- Local time
- Today, 11:47
- Joined
- Mar 14, 2017
- Messages
- 11,680
Maybe you can accept the results as-is (but make sure it's on the Query side), then use the properties in a Form or Report to make it a hyperlink again.
The reason why this happens is because, as Microsoft documentation says, LCASE() function returns a string
Functions always officially return something. Have to pay attention to what that something is.
This is another one in the dozens of scenarios that prove you should not use creative datatypes (like Hyperlink) in a database - including in quasi-databases, like MS Access. Store it as plain text and worry about the fancy stuff when working with the presentation layer - forms, reports, etc.
Query your text field as LCASE, then fancify it later.
Don't use formatting concepts at the table level - ever!
The reason why this happens is because, as Microsoft documentation says, LCASE() function returns a string
Functions always officially return something. Have to pay attention to what that something is.
This is another one in the dozens of scenarios that prove you should not use creative datatypes (like Hyperlink) in a database - including in quasi-databases, like MS Access. Store it as plain text and worry about the fancy stuff when working with the presentation layer - forms, reports, etc.
Query your text field as LCASE, then fancify it later.
Don't use formatting concepts at the table level - ever!
Pat Hartman
Super Moderator
- Local time
- Today, 14:47
- Joined
- Feb 19, 2002
- Messages
- 47,280
If you have used a hyperlink data type, you actually have two fields or possibly three. One for the user text. One for the actual link. And there might be a third. I never used the data type since it is incompatible with SQL Server.
Why do you care if the user types upper and lower characters?
Why do you care if the user types upper and lower characters?
