Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 
Not applicable

Section Access: allowed characters

Good day,

Our section access is based on NT logins.

Normally this works ok, but when usernames have special symbols, we're stuck.

ok:        Youssef

nok:      Odé

We tried with ODE and ODÉ, but neither works.

Any idea how to handle this?

Tnx, karel


1 Solution

Accepted Solutions
Peter_Cammaert
Partner - Champion III
Partner - Champion III

BTW where does you SA data originate? In an external file perhaps? Then this might help: Re: Hidden special character causing error in Section Access?

View solution in original post

3 Replies
Peter_Cammaert
Partner - Champion III
Partner - Champion III

That's weird, because AD ignores diacritic marks (this is by design, you cannot define both AndréLeroy and AndreLeroy as AD Logon Names because they are considered identical)

At least ODE should work. Maybe this is a genuine QV problem?

Peter

Peter_Cammaert
Partner - Champion III
Partner - Champion III

BTW where does you SA data originate? In an external file perhaps? Then this might help: Re: Hidden special character causing error in Section Access?

Not applicable
Author

Tnx Peter,

Changing load to (txt, utf8, embedded labels, delimiter is '\t', msq); solved the problem indeed.

karel