I have NOT had the problem since I did all of the R:Clean (not an official
name) Routines    

 

1.       look for dup dll's, renamed rbl's, lost RBIO's and dup etc..   

2.       Unload and Reload the entire database and watch for errors.

3.       Run a RRBYW14 or 15 and verify that it happens on that app as well.
(take two minutes and compile 15's RFF and test it separate also)

4.       And the one that works 99% of the time!   Create a new Windows
User.  

 

Sincerely,

Paul Dewey 

 

 

 

I should have posted a followup.   It has been a week or more now with out
any issues.

 

 

New Horizon Interlock Inc.

New Horizon Safety Diagnostics Inc.

www.interlockinfo.com

Saving Lives - One Breath at A Time  T

 

This e-mail message is intended only for the named recipient(s) above and is
covered by the Electronic Communications Privacy Act 18 U.S.C. Section
2510-2521. This e-mail is confidential and may contain information that is
privileged or exempt from disclosure under applicable law. If you have
received this message in error please immediately notify the sender by
return e-mail and delete this e-mail message from your computer. 

 

 

From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of
[EMAIL PROTECTED]
Sent: Wednesday, November 19, 2008 3:00 PM
To: RBASE-L Mailing List
Subject: [RBASE-L] - Compiled EXE not releasing from task manager

 

I believe there was a thread on this a while back, but a quick search did
not see any resolutions.

 

I have compiled apps that on occasion, do not release the EXE in the task
manager.  From the 

desktop, all seems to have shut down properly, but if you look at the task
manager, the EXE still

shows and often running 50% cpu.  This has been a long ongoing occurance,
but as I have been

adding users, so it is becoming more of an issue.

 

Example of a current instance.

 

User has the app setting at a main menu.  Has not done any transactions or
processes for an extended period of time, about 2 hours.  Then they pull up
a form that when a part number is entered, an eep

looks up a part description in a ODBC linked table.  They recieve an error
message that a value is not found. Although I have triple checked that it
does.   They then exit the form and immediately get a Access violation error
on RBG75.DLL.  They click OK and the program aborts out and disappears from
the screen.  However it still shows running in the task manager.  The same
user on the same machine can call this program up and do the exact same
sequence with the exact same data and it works without error 99% of the
teim, but on occasion errors out.  It seems to happen more often if the app
is left "untouched" for extended periods.  There are no timers and event
logs show no network disconnects.  

 

Another example is that the app is being ran and no errors are seen or
detected.  All forms and data reports as expected.  The user exits the app
and recieves no error messages.   The system might seem sluggish and when
they look at the task manager, again the EXE is running at 50% cpu even
though no indication of the app is seen on the desktop.

 

I have one station that runs the same app although uncompiled.  (Apps are
all form/eep based, the compiled app simply connects the database, presets
variables and calls  the MainMenu form.  The same cmd file that gets
compiled ran via the R> has never seen a hang up or issue.

 

Has anyone else seen these symptoms and / or found a resolution?

 

Thanks,

Bob

 

 

--
Thompson Technology Consultants 
LaPorte, IN 46350 
219-363-7441

 

Reply via email to