Question about net:storedataAs... Again

[oggy]

I have two applications on NT5.32. One of them have external data dll, other no.... First application, that one with data dll,  do not work very well. To simplify, that application does not use NetWebServerWorker.UtfToAscii    from netweb.clw ( I know that because I've put in original netweb.clw some debug messages). That application, netweb server, does not trigger any messages from procedure. Other application, the one without data dll, works just fine and trigger all messages from procedure. Because of that, first application does not show data in browses well (East Eurppe)
Any hint?
Regards, Ozren.

[Bruce]

NetTalk lives in the data dll.
So when you update nettalk, or edit the netweb.clw file, you need to recompile the data dll for the changes to take effect.

cheers
Bruce

[oggy]

Ok, I did it, and now app goes to NetWebServerWorker.UtfToAscii  procedure.... But, always that but... In dll-driven procedure, this not works well. For example: open some browse that contains east european character, all looks fine, but when scrolling to second page(s), the browse did not display well... This is just in application with data dll. In other application, all browses works well...
Example two: on login form in application with data dll, two fields (user name and password), the fields displays east european characters, but login source in background cannot "pass" checking no matter what I try. Other application, same way to check login name and password, all works fine.
TPS driver in both applications, one dictionary for both applications...
Please any hint, time is ticking ! And my wife is  so angry about my behaviour 
Regards, Ozren.
 

[Bruce]

perhaps you can post an example?

cheers
Bruce

[oggy]

OK, first I must apologies for posting, lets say, false alarm... Indeed, converting for East European character do not work well, but it is my fault. I finally realized that my changed version of NETWEB.CLW, with portion(s) of NetWebServerWorker.UtfToAscii  procedure was partially wrong. Some character(s) encoding (decoding) was wrong. In last few days I rewrote this and now it is correct for all these characters... I have in production 3 sites, one on, via ODBC, on FIREBIRD, and two on TPS driver... And all work well.
Mea culpa, I was too quick to post changed clw that I did not fully tested on real data ....
Once more, I apologies for this.
I have now NETWEB.CLW that is OK, may I posted or send it?
Regards, Ozren.

[Bruce]

send it to me please Oggy and I can fold it into the shipping release...

thanks for the update!

cheers
Bruce

[oggy]

Sended.

[Bruce]

thanks. I've updated in 5.33

cheers
Bruce