After much banging my head against the brickwall we all know as the RDK, I've reduced it down to this. Sometimes, for reasons known only to itself, the RDK either bypasses any BFS on Sysrepos or the BFS is not doing it's job. It appears, from process of elimination, that what is supposed to happen is that when the RDK extracts repository items, it decompiles the compiled repository item, and then when the repository items are copied back into the clients repository the BFS is supposed to compile it. This is spasmodically not happening. I have one particular window that when compiled creates an incredibly screwed up repository entry for the window executable. I've checked the integrity of both the SYSREPOS file and SYSREPOSWINS file, and found no errors there, the window itself is not overly large, (one page, and around 40 controls all up), and there appears to be nothing wrong with it. So what could be a cause for a window to not produce the correct repos item, consistently?

Tyler,

Just a wild guess: Maybe there is something in your windows that can be misinterpreted in certain circumstances?

Have you got static texts with more than one line?

I've never used the RDK, but I have some windows that were problematic in one other particular circumstance. Those windows have static texts with more than one line, and so the text entries in the SYSREPOSWINS rows contain some newline character(s). I once tried to edit the SYSREPOSWINS rows directly in Sys Ed, but then the rows became corrupted. So the newlines must have been converted to a different delimiter or something. Apart from this I have had no problems with those windows.

I also know of a couple of other instances when characters are misinterpreted as delimiters in window components. Tose were foreign characters, though.

I know there isn't much chance of me being on the right track here, but at least you know you have my sympathy.

- Oystein -

Tyler,

    Could you try making a repository view with only this window in it? Then do an upgrade/module deployment and then tell me what the results are.

1. DaveRevelation

Tyler,

It is possible that you have an invalid quick-event definition or a system delimiter or other illegal character in a control name; the SCAN_REP tool in 3.6 is designed to detect errors such as this, although it cannot identify the specific error within the window structure (SYSREPOSWINS) itself. However, I do not understand how the repository information could be stored in its text (not encrypted) format, as you have ascertained by viewing it from Advanced Revelation. From your message, I am not sure if you development system has it stored not encrypted, or if the deployed runtime has it stored not encrypted, or both.

Cameron Purdy

Revelation Software

View this thread on the forum...