hidden msaccess.exe in the task manager?

[smd7m]

Hi
What should be hidden msaccess.exe in the task manager then run Db.

 

[wiklendt]

please try to re-phrase your question or explain what you are doing.

 

[smd7m]

if run a database in your system then see Task manager processes list in the windows
you seen in the list is msaccess.exe.
Now, I will Hidden msaccess.exe in list or Hidden all program processing.

 

[wiklendt]

if run a database in your system then see Task manager processes list in the windows
you seen in the list is msaccess.exe.
Now, I will Hidden msaccess.exe in list or Hidden all program processing.

are you asking how to make it such that when someone runs your database, they WON'T see msaccess.exe in the Processes tab of the Windows Task Manager?

i'm afraid i don't know. maybe someone else does, if that is indeed a/the question.

 

[Atomic Shrimp]

Why would you want to do this?

I can imagine several possible reasons, but none of them good reasons.

 

[genesis]

I think one of his reason would be, he wouldn't want anyone to shutdown the access program abruptly because he want that the access project that he have to be close procedurally because maybe there is a code behind to be executed before quitting ms access.

 

[Atomic Shrimp]

That's a more decent reason than anything I had in mind, but still... if it is that, it seems like a workaround that probably means something should be done differently elsewhere in the application.

 

[smd7m]

thanks wiklendt, Atomic Shrimp, genesis

Question me:

when someone runs your database, they WON'T see msaccess.exe in the Processes tab of the Windows Task Manager?

Waiting for your reply.

 

[genesis]

I agree with atomic shrimp smd7m. you should change probably your design in your application. maybe there is some code that can be written for that but I dont. I dont discourage you.

I have same question like this before in my mind when I design how to setup my project expiry date that will not involving the registry keys but only inside my database. Before, I was also thinking that the user should not be able to force shutdown the access in the task manager that they should properly click on the quit event procedure so that before the application quits, an event will update the last date of the application inside the database table. but I set aside the task manager idea and change to something more just inside my project.

but I have one suggestion for you is you persist and that is to disable the task manager itself thru registry. When the application is open disable the task manager and when the application closes using the proper event procedure, re-enable the task manager.

 

[Atomic Shrimp]

Waiting for your reply.

My question:

Why would you want to do this?

 

[Kryst51]

I want to throw my two cents in here, for what it's worth, if the reason is to keep it from being forced to shut down, that's silly, a person could just shut off their computer, or unplug it from the wall. What I mean is that you can't control everything a user is capable of doing to shut down the program. You can only control how your program reacts. It's like in counseling, you can't change how other people act, you can only change yourself, I think the same applies here. There is always a way that you can't conceive of that a person can shut down a program. The task manager thing seems to be a little overkill. Of course, this discourse only applies IF the reason behind the question is to control the shutdown of your program.

 

[NigelShaw]

Hi,

The pessimistic side of me thinks differently. Looking over the recent thread & requests of this poster, they all seem to ask related questions.

"HOW CAN I DO THIS WITHOUT THE USER KNOWING OR HAVING THE ABILITY TO FIND OUT"

dont get me wrong, im certianly NOT pointing a finger or laying accusation but consider-

"a program to filter information from one computer to another and not giving the user any way of either knowing about it or preventing it"

A trojan maybe... who knows? i dont for that matter but the questions are a little over the top for a "new access user".

Viruses and trojans all have the same things in common.

"ability to run without user knowledge and difficult to identify" pretty similar to all of the questions asked already.


on the other hand, he might just be really concious of the program he writing

Nidge

 

[Kryst51]

"HOW CAN I DO THIS WITHOUT THE USER KNOWING OR HAVING THE ABILITY TO FIND OUT"

dont get me wrong, im certianly NOT pointing a finger or laying accusation but consider-

"a program to filter information from one computer to another and not giving the user any way of either knowing about it or preventing it"

A trojan maybe... who knows? i dont for that matter but the questions are a little over the top for a "new access user".

Viruses and trojans all have the same things in common.

"ability to run without user knowledge and difficult to identify" pretty similar to all of the questions asked already.

That's certainly something to think about, it does seem a bit underhanded doesn't it?

 

[wiklendt]

but I have one suggestion for you is you persist and that is to disable the task manager itself thru registry. When the application is open disable the task manager and when the application closes using the proper event procedure, re-enable the task manager.

i would immediately de-install, and refuse to use again, any application that prevented me from using normal windows tools, like the task manager.

 

[genesis]

it his choice.

but as have been said, it is most advisable to modify his design inside his project and set aside the task manager idea.

 

[Atomic Shrimp]

Hi,

The pessimistic side of me thinks differently. Looking over the recent thread & requests of this poster, they all seem to ask related questions.

"HOW CAN I DO THIS WITHOUT THE USER KNOWING OR HAVING THE ABILITY TO FIND OUT"

dont get me wrong, im certianly NOT pointing a finger or laying accusation but consider-

"a program to filter information from one computer to another and not giving the user any way of either knowing about it or preventing it"

A trojan maybe... who knows? i dont for that matter but the questions are a little over the top for a "new access user".

Viruses and trojans all have the same things in common.

"ability to run without user knowledge and difficult to identify" pretty similar to all of the questions asked already.


on the other hand, he might just be really concious of the program he writing

Nidge

These thoughts had crossed my mind, but in a slightly different way. A program that tries to do these things may end up being identified as malware by heuristic security programs - so even if the motives are all completely innocent, it might fail badly in the real world.

My take on these questions (and I'm glad I wasn't the only one to have noticed the emerging theme) was that this looks like a scheme to develop something in Access and try to make it look like a standalone program.

 

[Atomic Shrimp]

but I have one suggestion for you is you persist and that is to disable the task manager itself thru registry. When the application is open disable the task manager and when the application closes using the proper event procedure, re-enable the task manager.

i would immediately de-install, and refuse to use again, any application that prevented me from using normal windows tools, like the task manager.

I used to have arguments with my previous boss about this sort of thing - he had designed a program that had forms laid out in such a way that they didn't work properly unless the windows desktop properties were set just so - and he wanted the program to set them on opening and put them back on closing.
I strongly object to this methodology - for several reasons, including:

• Windows is a multi-tasking OS - the programmer should not assume that his application will be the only one open at runtime. Hijacking the task manager (or in my case, desktop appearance settings) impacts more than just the application that performs the hijack
• Restoring normality on exit may fail (or may just not happen at all, if the program terminates abnormally)
• Hijacking the system settings may work just fine on the developer's test rig, but may generate problems in the field, due to differing configuration on customer machines - or it may simply not work at all under certain security configurations