From Author:
Well I figured it out. My problem was two bugs. The first was I needed to code the upvar like this
upvar #0 Node[expr $node_nr] MyLocalNode
set thistest $MyLocalNode(NodeID)
The second problem was related because of the recurrsive procs. Each variable group on the stack needed...
From Author SORRY: Should read
I've also tried using the global command like this:
global Node[expr $node_nr]
set thistest ${Node[expr $node_nr]}(NodeID)
*******************************************
Actually, I've tried every possible combination of brackets and curlys.
I just want to...
I've got a recursive proc with code that access a global associative array. There are many associative arrays using the naming convention Node1, Node2, Node 3 etc...
Because the name has to be dynamically generated
upvar 0 Node[expr $node_nr] MyLocalNode
set thistest $MyLocalNode(NodeID)...
Using VB/ADO connecting to Sybase, I set up a new System DSN called "rightnow". Don't put in a default server or database. Add two or more comma delimited servers and databases in the connection tab of the ODBC mangager.
.ConnectionString = "DATA SOURCE=rightnow"...
I saw so much info on this error, going back and forth. I really don't know what using the TLBRegister does, but it works. Thanks.
I'll have to do some research on TLBRegister
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.