Home Forums Discussions Problems v4 not closing down completely

I know, I know, upgrade to v5. I just can't make myself do it yet. I just wanted to know if anyone had had this problem in the past where after you close the program down, and then try to open it back up, it is still running in Windows. I therefore have to CTL-ALT-DELETE and go into the task manager and close the program prior to restarting it.

Doesn't do it all the time and only on one computer that runs Windows Vista.

I vaguely remember having an issue with V3 like that on one computer. Try reinstalling it.

Does it all the time. Did it in v4 and now in v5. I just use Task Manager to destroy it.

V4, V5, XP, Vista, Win7....happens now and then with all of them for us.

and even V8

Travis,

Not much consolation, but you can bring up the task manager and then minimize it. Much easier to click on it on the task bar than to do the whole CTRL - ALT - DELETE thing.

OK. So I guess it just happens. It's easy to fix for sure. Just a nuisance and odd that closing the program doesn't close the program.

So demanding, Travis. Next I suppose you will want the program to start just because you click on it!

Travis,

One day when you have time, and you want to hear the horror story I lived through with v2 for over a month, I will tell you. I will give you a clue, The program did the same thing in v2, and if you add that to the mystery problem, it seriously was AC hell. I had to beg my partner not to drop it.

Jon you're right. I don't know what I was thinking. Surgeons are arrogant bastards and definitely too demanding. open=open, close=close, save=save. Maybe I'm asking for too much.

Bert: I don't think I could have gotten a single one of my colleagues at my previous practice to go with EMR at all so I can imagine trying to get someone go with it and have problems. The program would do it one time and it would be over. None of them would have a clue how to hit CTRL-ALT-DEL. "Paper doesn't do this" I can hear them say.

LOL. Well given you are in the "virtual" office of Travis, Leslie and Bert, I will give you the story when I get to the office. I have written it before, but I don't know where it is.

Ah yes, our virtual office. I love it. Your patients are better than Leslie's. Not usually nearly as sick and haven't had 65 years of neglect yet. Inguinal, umbilical hernia, and orchiopexy deluxe. Nothing better than a 7 year old appendectomy. Those kids bounce back in less than 8 hours and are ready to be out of the hospital. Of course, if your patients go bad, it's really really bad. Those little people have no reserve.

Our overhead is super cheap.

LOL. Yes, true. But, don't forget the parents.

OK, our story. It's hilarious now. But, not before. OK, on the server there was a little file analogous to Amazing Utilities. It somehow shutdown and restarted Access (yes Access).

Now, we had about 11 AC programs running. This was back in the v2 days I think. We loved the program. It just had this one problem. Let's call it the YSOD or Yellow Screen of Death for the color of AC. It would just happen. Maybe once or up to six or seven times per day. The program would just crash for no reason, freeze up and just die. But, not on just that computer. All 11. So, everyone would have to stop (after losing that note or the triage data the nurses were putting in), and I would have to run to the server, click on the file (which is now a shortcut) and restart the databases. Then all of the programs could restart which took what seemed like forever. So, how hard would it be to go around.

BUT....you couldn't restart the database UNTIL every computer was out of AC. So, everyone would yell, OK. I would click on it and nothing. Couldn't do it yet. So, everyone is running to every computer (even ones that no one was using) to close AC. OK! all closed. So, I would click on the utility and nothing.

So, this is where the error you are describing. Hasn't been fixed since then. There were some programs still running in memory. And, you could only tell, by pulling up task manager. There is was, so you would kill that one. OK, Bert, fire her up. Click on the utility. Nothing! Still an error message. Ahhh...the two computers which I am embarrassed to admit had users using Fast User Switching. So, while User A had shut down, User B had AC up in the background. So switch to User B, and shut that one down. OK, fire it up. So, finally, the utility would work, and the green light would be given out and everyone would turn out AC. Time: 10:47 am. The time of the next crash: Tick, tick, tick.

Your right. I avoided pediatrics simply due to the parents. I acutally thought pediatrics was what I would do when entering med school then my pediatric rotation I realized that the kids had parents.

I'm amazed you stuck with AC having that type of problem on a daily basis. Painful beyond all pain. I'm not even sure if it is funny this many years later. Stresses me out.

Yeah, Jon and I had many conversations trying to fix that. He told me there were two other people with the same issue. Ironically, I talked to one of them on here, lol.

The fix was ridiculous. It shouldn't have worked, but it did. I don't know why, and I only tried it because seven years ago, I knew little about computers and networking. But, I went out and bought the latest version of Access.mdb and installed on the server. Now, you don't even NEED the program on the computer for the database to work. But, it fixed the problem. I wasn't going to try to figure it out.

Oh, and yes, they have parents. But, in most of my cases, they have "a" parent. Sure, they have two, but one isn't generally around.

ROTFLOL

And old folks have "well-meaning" kids. Try explaining to a child that their 90 year old parent will never outgrow their senility.

I was the other person. Actually, I thought it was V1something, may have been V2. My associate gave up on AC because of the experience. It was a problem for about 4-6 months and then went away (?another upgrade with a different version of Access?) But it was a major headache when it was active.

I think my partner didn't give up, because he was oblivious to anything and everything. He just kept on typing while we were all in a frenzy.