Obscure "invalid table handle" error

[brett s]

This problem has me stumped. I have pruned down a script that started to produce an invalid table handle error to try and get to the root cause of this problem. I want to output records from a set to a table via some Xbasic code that just loops through the set. However, whenever I try and reference the pointer to the table I get the invalid table handle message. My pruned down code and the error message is shown in the attached jpeg.

There is nothing odd about this code, it's about as simple as it could possibly be. The table is not part of the set, in case you wondered. It's a simple table of 8 fields and one index.

Any clues as to the reason for this obtuse behavior by A5 would be much appreciated. Thanks.

[Lance Gurd]

Re: Obscure "invalid table handle" error

Brett,

is nqo2comp part of the nqocompany set? If so it is closed by the setin.close() command

[brett s]

Re: Obscure "invalid table handle" error

Brett,

is nqo2comp part of the nqocompany set? If so it is closed by the setin.close() command

Lance, no nqo2comp is not part of the set. I have swapped the two close statements around so that 'tbl.close()' is first. But I still get exactly the same error message.

I think the problem may be something to do with A5 using all memory space for the table handles in the set. So I need to be able to allocate more space manually so I can test this theory.

I am running A5v7 4130-3033 on Windows XP Pro and have 2GB RAM. So I can't do anything more here. But there may be an internal command to allocate additional table handle space in A5. Anyone know how to do this?

[Tom Cone Jr]

Re: Obscure "invalid table handle" error

Brett, have you used the debugger to see if other clues can be gleaned? This would at least confirm that the table.open() command is working as intended.

[ Added later ]
You must have something else going on. I can't duplicate the error you're seeing using AlphaSports and the following script (run from the Code pg of the control panel:

option strict
dim tbl as P
dim ncount as n = 0
dim set_in as P
dim product_ptr as P
dim vendor_ptr as P

tbl = table.open("salespeople")

Set_in = table.open("Invoice.set")
Product_ptr = Set_in.get("Product")
Vendor_ptr = Set_in.get("Vendor")
Set_in.fetch_first()
while .not. Set_in.fetch_eof()
	Trace.writeln("Product: "+trim(Product_ptr.description) +"; Vendor: "+trim(Product_ptr.vendor)+ "; Phone: "+trim(vendor_ptr.phone))
	ncount = ncount + 1
	trace.writeln("ncount: "+ltrim(str(ncount)))
	if ncount = 200 then
	    exit while
	end if
	Set_in.fetch_next()
end while

Set_in.close()
tbl.close()
end

Are any of the tables already open when your script runs? Are any forms open which rely on any of the tables?

-- tom

[Stan Mathews]

Re: Obscure "invalid table handle" error

Lance, no nqo2comp is not part of the set. I have swapped the two close statements around so that 'tbl.close()' is first. But I still get exactly the same error message.

I think the problem may be something to do with A5 using all memory space for the table handles in the set. So I need to be able to allocate more space manually so I can test this theory.

I am running A5v7 4130-3033 on Windows XP Pro and have 2GB RAM. So I can't do anything more here. But there may be an internal command to allocate additional table handle space in A5. Anyone know how to do this?

Testing here leads me to believe you need to use set.open_session().

[brett s]

Re: Obscure "invalid table handle" error

Stan. Yes, I was just about to post a message after discovering the set.open_session() command too. A5 appears to coral all the set tables into their own session and then assumes any subsequent reference to a pointer is a reference to a table of the set. So simply changing 'set.open()' to 'set.open_session()' fixed the problem. Yippee. :) The obscure error message didn't exactly help though.

Many thanks, Stan. Tom too.