<Return Thread> error??

[Howard G. Cornett]

When I close my database, but not Alpha Five, then restart my database, I sometimes get an error called "Return Thread" in my autoexec script. Anyone have any idea what this means?

Howard

[Howard G. Cornett]

Bump

Anyone??? It is happening again.

Howard

[Steve Workings]

Never heard of it. Can you track down which line of the autoexec is causing the problem? How about showing us that line or the script?

[Howard G. Cornett]

I'd love to!

Steve,

I would love to! Unfortunately, the system gives me absolutely no clue where the error is happening.

Howard

[Tom Cone Jr]

Howard check the things that load or open on startup. autoexec; OnInit and OnActivate events in the opening form; etc. If this never happens using AlphaSports it's probably ok to rule out a hardware issue with your pc.

-- tom

[Stan Mathews]

Steve,

I would love to! Unfortunately, the system gives me absolutely no clue where the error is happening.

Howard

Steve said, "How about showing us that line or the script?"

If there's nothing there that you have copyrighted and don't care to disclose, post the whole autoexec script, please.

[Raymond Lyons]

Although I have no idea what it means, based on it happening only on closing and then re-opening w/o closing A5, I would bet it has nothing to do with the contents of you autoexec script. I have not had your error but have had weird results when doing what you describe [also when closing one DB opening another via a5.load()].

This may or may not help but there is an internal script called 'on_database_init' that is run prior to the autoexec and the error may be coming in there. You can [maybe!] check this by running the attached code in a script (code by Selwyn, not me). I say "maybe" because your error only happens in a certain situation, so just running this script when your app is open probably won't reveal anything useful. Hmm, perhaps you could modify the script to close your app and then re-open it with a5.load(). Not sure how you would do that or if it is even possible. Like I said, "This may or may not help..."

Ray

[Marcel Kollenaar]

Obvious there are some threads started when your database is fired up but not stopped when the database is closed.

Write a small script to see the active threads before you start the database. And run it again when your database is closed but A5 still active.

Tip. Use THREAD_ENUM() function which returns a list of the names of running threads. This can be in the Interactive mode.

?thread_enum()
= Main

threadmon()

Or put the THREADMON() function in the autoexec script. It opens a small window listing the running threads. Takes an optional Refresh_Interval, which specifies in seconds how often the display should be updated.

It should list the threads even if the database is stopped. The thread that remains is the bad guy and you have more information where to look.

Threads (can) create error logs if the programmer has used it. Look for *.log. Maybe this lists something.

Look also in the Windows system errorlogs if something is listed.