vbs script file corruption

[fscommand]

Hello everyone,

recently I was debugging a problem which was [more like "ghoust-in-the-shell" effect] misteriously there without any reason.So what It came out after 2 day in front of the pc, is that my vbs script file was somehow went corrupted - by opening/editing it with Ultraedit or other text editor.So my question is, are there such issues by other users and perhaps such vbs script file corruption can be happening with other interactions with the file.

Please case so,make a list of a few things that can make a vbs fiel corrupted to avoid confusion. It can speed up the debugging a lot.

Thanks in advance.

[GINNI]

Hi fscommand,

 i searched for similar problems. I found one, who had nearly the same problem editing VBS with wordpad. I tried myself editing VBS with notepad, but it worked fine. So I think it depends on the texteditor or also possible the encoding you use. So I would just recommend to edit your scripts in DIAdem. 

Regards

Greg

[AndreasK]

Could you post a zipped version of your corrupt vbs file to see whats happened to it.

At the end I think it is related to the encoding. (Unicode/UTF16)

But I would like to analyze the file in a hexdump to see whats happende. Or is it completely destructed.

What I know is that some Source Control systems may desctroy files but even C++ or whatever if

they are trying to adapt the file to local settings like linefeed etc.

Greetings

Andreas

[blaze22]

If you are writing vbscript then you should use Microsoft VB program in which you are also provided with good interface for editing your script. When you write your script with other editor program then it is likely to be corrupted. However, if your file has corrupted then you can cure it using file cure software. The software repair and correct the corrupted file.