Multiple .DAT files

[rkligman]

I see that it is possible to call a different .DAT file from the command line. That is cool except I don't understand the ramifications of this.

Normal procedure is for the Update Client to validate the "sameness" of the Client Data on the Client and Server. So what happens when you call a different .DAT file? Does the Update Client still compare the original .DAT file to the Server .TS2 file or does it compare the running .DAT file to the .TS2 file on the server or ??

How does the Update Client know when this "other" .DAT file is out of date and how does it get updated? As you can tell, I'm a bit disoriented as to how the whole process works when you involve a different .DAT file.

[Mark]

Hi rkligman,

The dat file in TrueUpdate contains all of the client data, including TrueUpdate servers, Client Script, and Client Screens.

So when you run TrueUpdate 2.0 with the /DATFILE command line option, the update does not know anything about the other "original" dat file, and it will compare the TS2 file found on the server with the dat file specified in command line.

This shouldn't be a problem since the two dat files will generally have different server file prefixes and use different TrueUpdate servers.

[rkligman]

Well you seemed to have answered the question with a solution that made an assumption that could not have been made by a novice with the product. Reading your solution it seems fair that everything would be different but my initial thoughts when I read about this capability was that just the name of the .DAT file would be different but it would look at the same Server files. That would certainly be asking for trouble given your response.

I believe that these are now the things that your product is lacking, examples. the documentation is overall very nice but when it comes to implementation, the user is left wondering how or why we would use such options. Granted I've only spent about 6 hours with the product but still, if I had an example to refer to it would be great. Thanks for the response.

Originally Posted by Mark

Hi rkligman,

The dat file in TrueUpdate contains all of the client data, including TrueUpdate servers, Client Script, and Client Screens.

So when you run TrueUpdate 2.0 with the /DATFILE command line option, the update does not know anything about the other "original" dat file, and it will compare the TS2 file found on the server with the dat file specified in command line.

This shouldn't be a problem since the two dat files will generally have different server file prefixes and use different TrueUpdate servers.

[Mark]

Originally Posted by rkligman

Well you seemed to have answered the question with a solution that made an assumption that could not have been made by a novice with the product. Reading your solution it seems fair that everything would be different but my initial thoughts when I read about this capability was that just the name of the .DAT file would be different but it would look at the same Server files. That would certainly be asking for trouble given your response.

Yes, it would lead to trouble if both dat files looked at the same server and had the same name. The problem is that the server will generally have to contain a corresponding TS2 to one of the files, meaning that when the other is used, it would be updated.

Originally Posted by rkligman

I believe that these are now the things that your product is lacking, examples. the documentation is overall very nice but when it comes to implementation, the user is left wondering how or why we would use such options. Granted I've only spent about 6 hours with the product but still, if I had an example to refer to it would be great. Thanks for the response.

Thanks for the documentation suggestion, I have submitted it to our suggestions database. Ref: 11151