Selected rows

[MikeC]

Re: Selected rows

Tom, Peter,
What you both said, of course, makes sense.....but will test again as I seem to remember this preventing me from accessing the form when the "server" computer had the form already opened, thus preventing the problem.

But obviously I could have been mistaken considering both of you say that it cannot work!!! :D

I will post back after retesting in a day or so (most likely to prove you both right!).

[MikeC]

Re: Selected rows

Hi all,
I don't know why it works but it does (I obviously could not leave this testing until later!! :) ).

This application was built in version 5 if that makes any difference at all.
I have two computers networked. One has the full development copy of Alpha and runs the application. The other just uses the runtime and opens up the application across the network. I tested with and without shadowing. If the form in question is open on either of the two computers, it prevents the other from opening up the same form.

What am I possibly doing different from other network scenarios that allows this to work when apparently it is not supposed to??

[MikeC]

Re: Selected rows

Hold on!!! I inadvertantly gave the incorrect script for the OnArrive event of the button...

This is what is actually placed as the former did NOT work!

dim t as p
t=table.current()
status=t.is_record_locked()

if status
  cancel
  ui_msg_box("Attention!", "The Report Filters have already been opened by another user.  Try again later.")
  end
end if

[Peter.Greulich]

Re: Selected rows

t=table.current()
status=t.is_record_locked()
...

Mike, needless to say, if you first put a particular record into change mode and then test against that particular record, you can do what you say, but...seems like a really strange way to accomplish what you are after. If for some reason I wanted to do what you are doing, I probably would use a special table and set the value there to check against...but that's just me.

[MikeC]

Re: Selected rows

Peter,
The reason behind my creating this code was so that when networked, two (or more) users could not be choosing report filters/criteria at the same time...analogous to what this thread mentions in using the mark records and the problems that would ensue when more than one user could mark records.

My question(s)...and apologies to Gaby if this is not something that is applicable to the original question:

What, if anything, is inherently "wrong" (or what is strange about it!) with this VERY simple method that sure seems to work for the purpose I describe? And how would your method work easier or be more foolproof?

As I came up with this on only my second attempt at trapping this situation I am by no means wedded to it.

[Peter.Greulich]

Re: Selected rows

Peter,
The reason behind my creating this code was so that when networked, two (or more) users could not be choosing report filters/criteria at the same time...analogous to what this thread mentions in using the mark records and the problems that would ensue when more than one user could mark records.

My question(s)...and apologies to Gaby if this is not something that is applicable to the original question:

What, if anything, is inherently "wrong" (or what is strange about it!) with this VERY simple method that sure seems to work for the purpose I describe? And how would your method work easier or be more foolproof?

As I came up with this on only my second attempt at trapping this situation I am by no means wedded to it.

Sorry, Mike. I didn't mean to be critical. I guess I fail to see how this works in the way that you suggest. Perhaps you could explain the steps on how you implement this. Thanks.

[gaby_h]

Re: Selected rows

Finally... figured it out:
I was running in circles trying to do it with operations.... the solution is simpler.
In Action Scripting, category: Records, --> Mark Record, choose the level (Browse1 in my case).
That's it. To use it: in the emb browse, highlight the rows push the button and the records are marked.
I need to get some sleep now.