how to use SourceGear Vault Client and CPP-Builder

[Shapour]

Hi Community,
how can I Use the SourceGear Vault Client 5.0.3 (18802) in a cpp builder Professional Project.
(Borland® C++Builder® für Microsoft® Windows™ Version 10.0.2288.42451 Update 2 Copyright © 2005 Borland® Software)

thanks
shapour

[lbauer]

Vault doesn't support integration with Borland products, but you can use the Vault GUI Client for source control operations and do your development in CPP-Builder. Add your code to Vault with the Vault Client, then set the Vault Client working directories to the location of your project on disk.

[Shapour]

Hello Linda Bauer,

thanks for your Replay. The Vault works fine now, but I have problem with some files, and I don't know why.

if I want to see the changes in some files, I get following Error.

"File has a NUL byte at offset 8818; ths is not valid for encoding 'Western European (ISO-8859-1)'
the offset is not always the same !
...

I can compare another Cpp files without Error and this is a cpp file and not a binary file.
thanks
Shapour

[lbauer]

Are you diffing the files with SourceGear's Diff/Merge tool?

[Shapour]

no, I just want to compare and find the changes.

[lbauer]

if I want to see the changes in some files, I get following Error.

I could use more information on how you are trying to see the changes. Are you using a View command in Vault?

[Shapour]

I use "show differences" in Vault context menu. (using right mouse click)

[jeffhostetler]

File has a NUL byte at offset...

This message means that there is a 0x00 byte in the file.
DiffMerge is trying to import the 2 source files and figure
out the character encoding so that it can convert them to
UNICODE for presentation/analysis. Unfortunately, the NUL
byte is not a valid UNICODE character so the conversion
fails.

Most of the time that conversion error indicates that DiffMerge
was given a pair of binary files, such as images or MS office
documents.

There have been a few cases reported where there was a NUL
byte in a known source file such as yours that caused this
message. Usually, it was the case that there was a bogus
whitespace character somewhere in the file.

Can you look in the file at that offset and see if that is the case?

jeff

[Shapour]

thanks jeff,
but how can I find this offset?
is it the Line number ?

[jeffhostetler]

I guess that wasn't the most useful error message. Sorry.

The "offset" is the absolute index of the NUL byte in the file.
It is not the line number.

I'm not sure what the easiest way to find this is with the tools
you have installed on your system. If you have CYGWIN installed,
try using "od -c" or a "cat -v" on it. If you have EMACS installed,
you can search using ^S^Q^space. I've not used Borland's tools,
so I don't know what editing/inspection tools they have. Usually,
you can just eyeball it in an editor.

jeff