on 04-24-2008 9:33 AM
Dear Forum,
Has anybody encountered this error ?
A date format issue ? If so, where to solve ? We have reset the dateformat to yyyy-mm-dd within Windows SQL Server. Still doesn't work.
Thanks for investigating
Sam Szafranski
hi everyone,
I answered my own question .... sometimes that happens
Config - user defaults - user default - date format --> was not configured properly.
That's it
Regards,
Sam
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for the quick response.
We're investigating the support pack issue for our 5.2 installation. What is the latest anyway ? SP8 ?
What we do know, is that LDAP is not being used.
Thanks in advance
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
if you are talking about LDAP integration and have a different date format, you must do a mapping.
Set the "Date format" to the one of your LDAP, e.g. dd/MM/yyyy. This mapping was case-sensitive, I don't know if it still is.
Regards,
Daniela
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This sounds like an Access Control 5.2 bug that has been fixed in a support pack.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.