You should test for is in read only mode and if so unload record/ set to read
write and then load
Regards
Chuck
Chuck Miller Voice: (617) 739-0306
Informed Solutions, Inc. Fax: (617) 232-1064
Chuck,
You and Chip were actually close. The issue wasn't with the table being in
read only but rather the way I was dealing with loading the record if it
was 'locked'.
"If Locked returns TRUE, then the record cannot be saved because
- it is locked by another user
- another process
- it is
OK here goes. Given the following code
You will see that
$proc=0
and
$user,$session,$name are all blank
*READ ONLY*([Table])
*Get a record*
*FIRST RECORD*([Part])
*LOAD RECORD*([Part])
*If *(*Locked*([Part])
*C_LONGINT*($proc)
*c_text*($user;$session;$name)
*LOCKED
What I am saying is if a table is in read only
Sent from my iPhone
> On Oct 11, 2018, at 4:18 PM, Kirk Brooks via 4D_Tech <4d_tech@lists.4d.com>
> wrote:
>
> Chuck,
> Well that supposes that the Locked command is not accurate. If that's wrong
> I'm not sure how to prove that. And that would be
Chip,
These aren't new records and in this case there aren't any transactions.
On Thu, Oct 11, 2018 at 11:48 AM Chip Scheide via 4D_Tech <
4d_tech@lists.4d.com> wrote:
> if the record is new - other processes can not see it.
> if the record existed before the transaction, then it should show
Randy,
Agreed, but why won't Locked By provide information about it?
On Thu, Oct 11, 2018 at 11:17 AM Randy Jaynes via 4D_Tech <
4d_tech@lists.4d.com> wrote:
> My first thought is transaction in another process somewhere.
>
> Randy
>
>
Chuck,
Well that supposes that the Locked command is not accurate. If that's wrong
I'm not sure how to prove that. And that would be a much more profound
problem, I think. But perhaps. I'm just assuming the issue is with the
Locked By command.
To be clear my method tests for Locked first:
Case
I bet that is it. As I recall, in this instance locked by returns nothing
as it is not reallty locked
Regards
Chuck
On Thu, Oct 11, 2018 at 2:48 PM Chip Scheide via 4D_Tech <
4d_tech@lists.4d.com> wrote:
>
> beginning (I think) in v13 - if the table is read only, a selected
> record shows as
if the record is new - other processes can not see it.
if the record existed before the transaction, then it should show what
process/user/etc has hold of it.
beginning (I think) in v13 - if the table is read only, a selected
record shows as locked.
Chip
On Thu, 11 Oct 2018 14:17:45 -0400,
Read only
On Thu, 11 Oct 2018 10:48:12 -0700, Kirk Brooks via 4D_Tech wrote:
> I have a method that tests if a record is locked and if it is attempts to
> figure out by whom:
>
> $text:="["+Table name($1)+"] "
>
> LOCKED BY($1->;$process;$4Duser;$machineName;$p_Name)
> PROCESS
>
My first thought is transaction in another process somewhere.
Randy
--
Randy Jaynes
Senior Programmer and Customer Support
http://printpoint.com • 845.687.3741 • PrintPoint, Inc • 57 Ludlow Lane •
Palisades, NY 10964
Please
Kirk
In 15 I had found you could lock records think you unlocked them and then
unloaded but they would remain locked until you quit server. What happens in
your car if you select a different record. Do both show as locked only first or
only the second
Regards
Chuck
Sent from my iPhone
>
12 matches
Mail list logo
