Drew Wutka
DWUTKA at Marlow.com
Sat Jul 28 03:47:38 CDT 2007
Ya, I'm just dying to start using Vista! <rolling eyes> When will people learn that the tighter the security, the less user friendly it is! ;) Drew -----Original Message----- From: dba-vb-bounces at databaseadvisors.com [mailto:dba-vb-bounces at databaseadvisors.com] On Behalf Of Michael Maddison Sent: Friday, July 27, 2007 8:20 PM To: dba-vb at databaseadvisors.com Subject: Re: [dba-VB] Odd problem with VB 6 application Hi Drew, Interesting. I only use early binding so the exe must be registered anyway. However I ran into a situation a few weeks ago in a TS environment (2003 or 2K I don't remember) where I had released an update of the ax.exe and after the client copied the exe to the server somehow the registry entry was set in such a way that only he could run the ax.exe! He says he can't remember what he did ;-/ Normally, unless I break compatability (stuff happens), just copying the new ax.exe is enough. BTW, just wait till your users move to Vista. Regsvr32 will not run by default even when you are logged on as local admin... ;-) You have to disable UAC. Not sure about regserver, but I assume it's the same. cheers Michael M To: dba-vb at databaseadvisors.com Subject: [dba-VB] Odd problem with VB 6 application This is just an FYI to the VB list. A week ago I made a modification to a system I've been working on called the ISFE. The ISFE was monitoring for new requests and a few other things, but that background process was slowing the interface down a bit. The modification I made took those processes and put it in another .exe (and the two talk through window messages, something I posted on the AccessD list). Anyhow, a few days ago, someone submitted a request saying they were getting the following error message 'Unexpected Application Error; quitting'. Here's what caused the problem. The new 'monitor' application was setup as an ActiveX .exe, because I created a generic 'event' class that each monitor event was built on (implemented). The main application tells the monitor application what monitors to start (based on the users role) by sending the class name. The monitor application then used CreateObject with that string. Can only do that in an ActiveX .exe. Turns out, however, that a standard User in a 2000 or later environment cannot start an ActiveX .exe for the first time, because the ActiveX .exe tries to register itself, and users with the basic User permissions don't have the ability to do so. If a power user or admin runs the program first, then the users can run it...go figure. Just figured I'd pass this along in case anyone else is using VB 6 still. Drew The information contained in this transmission is intended only for the person or entity to which it is addressed and may contain II-VI Proprietary and/or II-VI BusinessSensitve material. If you are not the intended recipient, please contact the sender immediately and destroy the material in its entirety, whether electronic or hard copy. You are notified that any review, retransmission, copying, disclosure, dissemination, or other use of, or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited. _______________________________________________ dba-VB mailing list dba-VB at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-vb http://www.databaseadvisors.com _______________________________________________ dba-VB mailing list dba-VB at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-vb http://www.databaseadvisors.com The information contained in this transmission is intended only for the person or entity to which it is addressed and may contain II-VI Proprietary and/or II-VI BusinessSensitve material. If you are not the intended recipient, please contact the sender immediately and destroy the material in its entirety, whether electronic or hard copy. You are notified that any review, retransmission, copying, disclosure, dissemination, or other use of, or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited.