On Tue, Jul 23, 2019 at 12:36 PM Ken McGinnis wrote:
> We could try to lock the exe and that would fail so we would know
> someone else is using the software. However, if that other user is
> working with data in a different folder, we don't care so we do not want
> to lock the exe.
>
Create a
Jürgen,
You are cordially invited to adjust the code with a try...catch. Would you
wind when you have updated that procedure to upload it here? I can than
also refresh my basic library.
Thanks
,
Koen
Op di 23 jul. 2019 om 15:31 schreef :
> Hi Koen,
>
> now that's a very old coding style.
Hi Koen,
now that's a very old coding style. Probably from the time before TRY/CATCH
was invented.
wOOdy
-Ursprüngliche Nachricht-
Von: ProFox Im Auftrag von Koen Piller
Gesendet: Dienstag, 23. Juli 2019 20:32
An: ProFox Email List
Betreff: Re: vfp9 exe
Hi,
you can make use of Craig
Hi,
you can make use of Craig Boyd's procedure, you shall have to parse your
DBC for every file to find if anything in use and than you can make a
message to the other users to please quit the application.
But, but, but. Why do you need to reindex? That should be a flaw in your
design. Please
Why not create a single file - with a single record, a File Lock Flag.
So - when a user goes to reindex files - they MUST Lock that one record
1st. Then, at the startup of your system - for regular users - the
system must check that flag & record to see if someone locked it and is
indexing
We have a vfp9 SP2 program that has been running nearly bug free for
over 10 years. Only now we have a need to find out if anyone else is
using the exe in a specific folder. We allow many users to have their
own unique folder with their patient data files.
So we log into folder 1 and another
You need to change the settings on the monitor itself. It normally rescales
automatically if you send him non-native resolutions, thus you need to set
the monitor to "Do not scale".
[excessive quoting removed by server]
___
Post Messages to:
7 matches
Mail list logo
