Error: invalid table handle

[Richard Froncek]

Have been this running a report for years. Suddenly I get the error message that tdailyrpt.enter_end() is invalid. The code is 510 lines, the enter _end is line 508.
Going backwards. V7 seemd to have problems that couldn't be resolved. Went back to V5 (latest version on Windows 2000). Suddenly, the report doesn't run. It will run in V7 with the exact same coding. The next line closes the table, but if I comment the enter_end, I get the same invalidtable handle for the close.??? Two steps forward, three back.
Have compacted any number times. Exited and returned. Cold boot and return with no change in the sudden appearance of the error message.
Dick

[Finian Lennon]

Do you have an "xbasic_wait_for_idle" anywhere in your code?

[Richard Froncek]

No. They're practically all just moving data from one table to another for a report.
I believe I found the problem; however the solution appears to be non trivial.
As I mentioned, there were 510 lines. I restored an earlier version with fewer than 500 lines in the script, around 476, as I recall. Since I really need the 510, I started adding lines, about 6 at a time. The report ran fine each time, until the last successful run at 497, I believe. Added a few more, and it went South. Once the error appears, it appears cast in concrete. Specifically, I have backed down to 467, mostly by moving comments from separate lines to the end of lines. Still, no matter how few lines I get down to, the error appears. Compacting does not help.
I don't recall ever seeing anything about a 500 line limit. I'll break it down into two scripts, one calling the other. However since it now seems "tarred and feathered", I'm not sure this will provide the solution. Will give it a shot. If the two pieces don't work, guess it'll be back to an earlier version and again add the lines for the umpteenth time, in two scripts.
Dick

[Tom Cone Jr]

Dick, good luck unscrambling this. Years ago I remember threads (a5v4 or a5v5 forum) where folks were hitting a script length limit in the code editor. If memory serves it was in the vicinity of 1,000 lines, but folks finally decided that it was not a line limit, it was a total character limit. Don't recall more recent threads discussing this, and don't know if the editing buffer has been extended in more recent releases. Thought I'd mention it in case you wanted to do a bit of searching.

In my own work I try real hard to limit scripts to one typed page each. This is about two screens full, or a bit more. If I'm going beyond that I'll break it down into separate scripts or functions. Have found that it's easier to trouble shoot and easier to maintain. Using custom (UDF) functions also helps to eliminate timing issues with scripts that keep working even though earlier processing has not been finished.

-- tom

[Richard Froncek]

Thanks Tom. I did break it downinto two scripts. The first is 353 lines. Midway (?) it calls the second, which is 130 lines. A total of 483 lines.
You're probably correct about the number of characters vice lines.
Rather than "breaking" in the middle, guess I'll try just splitting it in two, i.e., sequentially and see if that works. Conceptually, I'm not sure if there is a difference, but what the heck, I'll give it a shot.
Thanks again Tom.
Dick

[Richard Froncek]

Nope. Only a total of 318 lines now. Comments moved to places following statements. (Part 1). Still get invalid table handle (running only the first piece).
Copy script to notepad. Delete script. Compact. Exit program. Create "new" script from "old" code. Apparently, once the error label is attached. There's no getting rid of it.
Good thing I'm on the first level, so junping out the window won't cause any harm.
Dick

[Richard Froncek]

Eliminated all comments. Same story, "invalid table handle."
Dick

[Tom Cone Jr]

Dick, if you'll put the comments back in perhaps some of us will be able to help troubleshoot your script. We'll need the database, and instructions from you on where to look to find the script. A narrative description telling us, step by step, what you want your script to actually do, will also be needed.

-- tom

[Richard Froncek]

Will try and put it together as you suggest. Keep checking it as I go along, removing comments, and then suddenly it's back to the error message.
It'll be at least tomorrow before I get it posted here.
Thanks again Tom.
Dick

[Richard Froncek]

DailyRpt "Backup" provided. I have the db in c:\dailyrpt.
1) "H" on the main menu will take you to the form Sales & Marketing
2) For testing, step 1 may be omitted and go directly to the Sales & Marketing form (in Control Panel from Code to Form tab). Select "B" CME Daily. Enter '8' for the week (the last available), and your initials, or blank for the 'Send To'. Not sure how I got the request for the week in twice, or if it's necessary twice. The report should run. Since we're at the begining of a "new" week, the first two sections will be blank. I've left out the header with the customer's name, etc.
3) Although the form has been run for several years, a modification is required. The reason - the butter
market has expanded to include Tuesdays and Thursdays. Formerly it was only active on Monday, Wednesday, and Friday. The table has been expanded to account for the new fields required.
a) The script will be found in the code tab under "DailyStat". Adding the necessary code apparently
takes it to too many lines, or as Tom Cone suggested, possibly too may characters. However, once it
"blows", because of 'invalid table handle' tdailyrpt.enter_end()), it appears stuck on that error message, no matter how much backtracking is done.
b) I've included a "from here" to "to here" as a suggestion where the script might be broken into two
pieces. (DailyStat2 which would be called (Script_play() ).
c) The 'Bdays' (Butter Days) is no longer necessary. It and references to it can be removed. Further,
the checking code for the day in the butter section may also be removed.
d) Without the comments, it would be a real headscratcher looking at the code at a later date.
e) As the week goes on, the market may be checked daily after noon. "K" on the main menu will do it.
Unfortunately, while it will provide the data, the form will open, but the data will not be entered, as it's
supposed to do. In V7, I can also get the butter, but it also does not fill in the fields on the form. As mentioned earlier in the thread, problems have caused a retrograde back to V5. Of course you can fill in the dailymkt manually after joting down the numbers. Or of course you can make up your own, e.g., through Wednesday to see how the first two sections are working.
Hopefully, the foregoing provides all the essential elements of information. If not, to avoid cluttering up the thread, you can email me at [email protected].
Thank you.
Dick

[Richard Froncek]

Week 7 can be entered at the button to fill in the first two sections.
For testing, it's faster to use the "Run" icon in the Design mode of the script.
Attached is a zipped file of the script with many of the Tue & Wed expressions in place. It aborts with the invalid message. Provided for possible copy and paste rather than typing.
Dick

[Richard Froncek]

Will try attachment again.
Dick

[Richard Froncek]

Thanks to Tom Cone, I'm well on the way to a workable report. Per his suggestion, I'm breaking the original long script into a number of pieces. As the task proceeds, everthing seems to appear on course. The report is generated and so far has not aborted.
Thanks again.
Dick

[Finian Lennon]

I'm reasonably certain that the problem is not the length of the script or the number of characters. I have a number of 1000 line + scripts that run without problem. I seem to recall Cal Locklin also saying that he had several of over 1000 lines.