New DIAdem 2017 SP1 installation throws "bsrepVariableIsUndefined" error when TDR opened

[Chris_P_SD]

I keep seeing this error on a new installation of DIAdem 2017 SP1 64 bit on a Windows 7 computer when loading any TDR layout.  I couldn't find any background info on where the "bsrepVariableIsUndefined" gets defined.  The TDR layouts don't cause this error on other DIAdem installations.  Does anyone know what causes this?

.

[winner · Accepted solution]

Hi Chris_P_SD

This looks like a mixture of different DIAdem versions. Did you copy any files from a different DIAdem version to this folder or did you use a bar  definition of other DIAdem versions.

I could not reproduce this error. So you might try to uninstall and reinstall DIAdem (you might delete any remaining files in the DIAdem folder). But you might first try to reset the bar definition. To do so open the topic "Merge Bar" (Basics > General > Basic Information > Merge Bar) and click the link "Restore default bar definition".

Hope this helps

Winfried

[Chris_P_SD]

Thank you Winfried.  The DIAdem 2017 settings were indeed copied from an older installation.  I don't understand how the bar manager was interacting with the REPORT TDR's, but your recommendation seems to have resolved that "bsrepVariableIsUndefined" error.  For some reason I still get a "DIATxObj.dll" error when I load the report layout from within a script, but pre-loading the report layout then running the script works without error...

Thanks!

Chris

[winner]

Hi Chris,

I don't know how you copied the settings from the previous installation. If you just copied some files, they could cause this error. If you want to import old bar definitions, you can use the import link in the help file I mentioned above.

Winfried