Harald,
I followed the recommendation in your link and got the following result:
C:\Python26\dist>golden.exe
Traceback (most recent call last):
File "golden.py", line 2, in
File "winsys\registry.pyc", line 39, in
File "winsys\security.pyc", line 42, in
File "winsys\_security\_to
Ron,
> I followed the recommendation in your link and got the following result:
>
> C:\Python26\dist>golden.exe
>
> Traceback (most recent call last):
> File "golden.py", line 2, in
>
> File "winsys\registry.pyc", line 39, in
> File "winsys\security.pyc", line 42, in
> File "winsys\_se
On 31/03/2010 10:59, travel europe wrote:
Harald,
I followed the recommendation in your link and got the following result:
C:\Python26\dist>golden.exe
Traceback (most recent call last):
File "golden.py", line 2, in
File "winsys\registry.pyc", line 39, in
File "winsys\security.pyc", line 42, i
Re!
Sorry for late, but I have work for 35 hours, each day...
The problem was WS_EX_LAYERED.
I used that:
s=win32gui.GetWindowLong(self.hwnd, win32con.GWL_EXSTYLE)
win32gui.SetWindowLong(self.hwnd, win32con.GWL_EXSTYLE, s |
win32con.WS_EX_LAYERED)
but WS_EX_LAYERED must not used alone
Hi,
I have a script that runs smoothly on a local copy of an excel workbook. I want
to implement this so that it can access a shared version of the workbook but I
would like to kick out any users that currently have the shared version open.
Is it possibly to kick out any users with an open
hitheam mohamed wrote:
>
> I have a script that runs smoothly on a local copy of an excel
> workbook. I want to implement this so that it can access a shared
> version of the workbook but I would like to kick out any users that
> currently have the shared version open. Is it possibly to kick out an
