Hi Bruce,
>>what version did you upgrade _from_ ?
Was 11.35 and today updated to 11.47.
>> Generally speaking setting store-as to utf-8 is not ideal in Clarion 11 and below because (extended ansi) data stored as utf-8 cannot be displayed on a Clarion window or report. So generally I advise against setting store-as to utf-8 for old clarions.
It's on "Capesoft/NetTalk/NetTalkWebFunctionality.htm" "Web Server Procedure Extension" describing "Advanced Tab". Ok.
Web51 example is working even with store data as utf-8 or portuguese.
>> a) you have the login screen open in your browser, and then you are stopping (compiling?) starting the server. That login screen will then fail (because the server doesn't know what you are looking at.)
Initially I was closing tab, reopened and test but when trying traces end up compiling and starting server with screen opened. Now I'm closing browser, open new tab and test.
>> b) In the login procedure there is a call to SetSessionLoggedIn(false). This line can clash with a security setting (change SessionId on log in/out). So if you have this line, comment it out.
There's one call on "Generate Form" routine, but it doesn't make any difference.
Before calling ds_LogInUser all UserLoginOptions are correct but result is zero that I suppose that it didn't found the user. Is Charset could affect GUID in dssw5.tps?
Thank you.
Regards,
Marcos