I would like to kick that no-good elusive file.
I checked and even used a utility that's digs deeper into Task Manager to which handles and dll's are called and still could not find the one. We killed them one by one and at a suggestion (forgot who - sorry L ) I asked my service tech just to create a new user after three days of digging. I really thought that would not be the answer and YET it was. I still wish I could have found that problem file or dll but it is not time possible. It may have been a left over from a virus program and yet two machines in fact had other virus programs running. Now they are both Symantec's Enterprise. I have had SE since day one and these two had others and switched but I could not blame them. I have 2000, XP-Home, XP-Pro, Vista-Business all running on a Linux box and there is no common thing between any of them. I would say Vista has never caused a Task Manager error like we are talking about! This also includes several laptops off site, so I assume it is not just a local virus thing. Like I said, I wish I knew, but after creating new users on those affected by this strange behavior "No More Problems!" I wish I had better news but the change of users took about a good day. 8 affected and I think at last count all are good now. At least I have not heard anything. These are all compiled RBase apps and 4 of the 8 are networked, 4 off-site not networked. We used LogMeIn on those and fixed them via remote. (I am not promoting LogMeIn any more than any other remote desktop or VPN / tunnel). It is something in the OS and I asked even some IT engineers to help and besides checking code (which is why I compiled RRBYW15 -.rff) and then I figured it could not just be my issue. Or Razzak was wrong ;( and -- that is like finding a needle in the slopes of Vail, Keystone and Jackson Hole all put together! <lol> Sincerely, Paul Dewey If I ever find the file, I will post it! - Create new user gone. Yep! " Steal underware - - Make Profit!" Just that easy. 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 4:10 PM To: RBASE-L Mailing List Subject: [RBASE-L] - Re: Compiled EXE not releasing from task manager I will triple check for duplicate files, perhaps something is lurking out there somewhere. I have done a unload/load routine, but not often. Rbase is very stable and I do not seem to have database data issues. Since this never has happened on regular Rbase sessions, only on compiled apps, I assume it is not data related. (But could be mistaken) Creating new users is not really an option. I have 20 plus and this seems to happen occasionaly on all of them. Perhaps an elusive file is out there that I have not spotted so far. Thanks.. -- Thompson Technology Consultants LaPorte, IN 46350 219-363-7441 -------------- Original message -------------- From: "Paul InterlockInfo" <[EMAIL PROTECTED]> 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
