Well, I guess the question is... why do you need so many globally scoped persistent variables that persist from test run to test run? To be honest, that seems like an excessive number of globally scoped variables, persistent or otherwise. What are you using them for?
If this is a limitation built in to TestComplete, then I don't think there's a "work around" available... however, I just tried this... I was able to add 65 variables and I still haven't hit a "max limit". So... I guess the question is, how are you adding the variables? In my quick test, I just right clicked on the Persistent Variables section of my project suite and selected "new item".
Thank You
There are so many screens in our application under test has controls with dynamic identification properties, more over there are multiple instances of same control will be present on same screen. Direct name mapping of each control is tedious here, instead name map one of the control from a group of similar controls and use the project level variables to identify varying properties to distinguish which GUI control to access by run time decision. Added more persistent variables to distinguish each control type and screen.
I am also adding new variable just by right clicking and picking the New Item menu. However I am loosing existing variables when I add new one.
(My project had 33 Project level temporary variables in use)
