VBScript template wrong encoding

This forum can be browsed by the general public. Posting is limited to current SAPIEN license holders with active maintenance and does not offer a response time guarantee.
Forum rules
DO NOT POST LICENSE NUMBERS, ACTIVATION KEYS OR ANY OTHER LICENSING INFORMATION IN THIS FORUM.
Only the original author and our tech personnel can reply to a topic that is created in this forum. If you find a topic that relates to an issue you are having, please create a new topic and reference the other in your post.

Any code longer than three lines should be added as code using the 'Select Code' dropdown menu or attached as a file.
jvierra
Posts: 14344
Meble kuchenne na zamówienie - na wymiar - Wrocław
Joined: Tue May 22, 2007 9:57 am
Contact:

VBScript template wrong encoding

Post by jvierra »

sapien_vbscript_enc.jpg
sapien_vbscript_enc.jpg (46.97 KiB) Viewed 3046 times
Product, version and build: since at least 2015
(*** Please do not write "latest" as a version, specify a version number ***)
32 or 64 bit version of product: both
Operating system: all
32 or 64 bit OS: both

FYI - not a big problem but...

For at least the last three versions of PromalScript (2015/15/17) the vbscript file template has been set wrong. On each update tot the template I ned to open and save it as "ANSI" as it is set to "Unicode little-endian" which is not usable in Windows with WSH.

User avatar
Alexander Riedel
Posts: 7336
Joined: Tue May 29, 2007 4:43 pm

Re: VBScript template wrong encoding

Post by Alexander Riedel »

Not sure why you would say it is not usable.
It works just fine.
VBS Unicode.png
VBS Unicode.png (205.7 KiB) Viewed 3044 times
Alexander Riedel
SAPIEN Technologies, Inc.

jvierra
Posts: 14344
Joined: Tue May 22, 2007 9:57 am
Contact:

Re: VBScript template wrong encoding

Post by jvierra »

Thanks Alex,

My mistake. I have been changing it since 2014/15 because it was once set to Unicde - big endian which will not work on WS2008 and earlier system. "Little - endian works.

Sorry for the misdirection. I should have retested before I decided to post.

I hope I won't be fixing VBScript for too much longer.