> is working like >= on FIND action

Aware2014

Might anyone have an insight or work around to the following?

I've set-up two HTML links in a form. Basically to act as 'Previous' and 'Next' buttons. The 'Previous' works fine. However, 'Next' shows the same instance.

Previous - this works fine

FIND Marbles WHERE Marbles.ID < ThisMarbles.ID
 VIEW Marbles USING ShowMarbles NOEDIT

Next Rule - this does not work. It shows same instance

FIND Marbles WHERE Marbles.ID > ThisMarbles.ID
 VIEW Marbles USING ShowMarbles NOEDIT

I had inserted DISPLAY MESSAGE Responses.ID in the 'Next' rule in various places to see what was being captured and I noticed that it would display the current instance (ThisResponses.ID) as well as the instances that are greater than the current instance. Basically > would work like >=

Thoughts?

Aware2014

Update - actually the previous is not working as expected either. Originally I thought it was but only had two instances to work with. I added a couple of more and noticed that it is not working as expected.

If anyone has thoughts on an HTML button to 'walk' up and down instances I would appreciate it.

Aware2014

Getting late here - sorry. I meant Process Rules for Previous/Next logic for viewing a form that would be great. I have the HTML calls to the processes working. Its just the Rules that are not.

rocketman

Try THAT instead of THIS, I think the Australians work arse about face to the rest of the world.

Might be wrong but I'm pretty sure THAT is the last item in the context (ie the one you are looking at)

rocketman

Page 63 in the user manual. Actually - having just read it again after a couple of years, I don't think you need THIS if you are triggering this from a form (because the instance of Marbles you are looking at should be in its own context So

FIND Marbles WHERE Marbles.ID < Marbles.ID should work

rocketman

er ... actually start at page 59

tford

You probably need to also add TAKE BEST 1 at the end of your FIND action.

Aware2014

Thanks for those suggestions.

I've now tried This and That and neither. All similar results (not desired result).

tford

Your process for viewing an instance can also store the ID of the currently viewed item in an attribute of LoggedInRegularUser. Then the FIND can compare to the LIRU attribute so THIS and THAT are not even an issue.

rocketman

Following Tom's thread try

FIND Marbles WHERE Marbles.ID > Marbles.ID order by Marbles.ID ASC TAKE BEST 1

(Use DESC. For the reverse traversal)

Aware2014

Thanks guys - will be trying today and will report back findings.

Aware2014

OK - I've tried these options and still experiencing very odd behavior, as follows:

Even when not using 'This' on the FIND and instead storing the ID in a LIRU attribute it increments on instance (for the 'Next' link). But any subsequent instances do not work.

I set TAKE BEST to 3 and it indeed shows 3 instances in sequence when I click the 'Next' link. However, when I set TAKE BEST to 4 or more or remove TAKE BEST completely, it only increments 1 and no more.

This tends to tell me that there may be a BUG in the FIND feature potentially.

Thoughts?

tford

It will be easiest to help you if you post the specific syntax you try, followed by specific results.

rocketman

Hi Aware2014,

I understand what you are trying to do but cannot understand why you need to make life so difficult for yourself. Is it absolutely essential that you open your Marbles form in a modal window?

Please review the short video I've posted on Youtube. It is not a tutorial, just a small demo of what is achievable using standard layouts, queries and target panels - and standard forms with no additional html code

http://www.youtube.com/edit?o=U&feature=vm&video_id=0i93GMb-Eng

customaware

Cannot see the video rocketman.

Aware2014

Hi Rocketman - would love to see the video demo. Link does not appear to work.

At the moment (unless I see something in the video) it does appear that a modal window is the approach I am looking for.

Hi Tom, I will post more concrete syntax, etc. Running through several other workarounds at the moment.

Thanks for all of your help. If the product would just allow VIEW to work in Process just as the VIEW Object does in a Forms Operation this would all be solved. Because essentially I am trying to prevent the users having to do two click downs to get the View form.

Aware2014

Rocketman - just looked at the video (had to search in youtube for 0i93GMb-Eng)

First, nice app.

Your video starts off with a query on the bottom left and only after selecting a instance does it show the form on the bottom right. The issue I am trying to avoid is having to show users a query from which they have to select. I want it to start straight on the form already (without having to select something first). It would start at the first record. How can that be accomplished?

rocketman

ooops - wrong link

http://www.youtube.com/watch?v=0i93GMb-Eng

tford

I want it to start straight on the form already (without having to select something first). It would start at the first record. How can that be accomplished?

Something like:

FIND BO WHERE BO.Date=LoggedInRegularUser.SelectedDate ORDER BY BO.Date TAKE BEST 1

VIEW BO.Date USING Main

In this example, the FIND action will pick one instance of BO based upon the criteria you use & VIEW that instance.

Aware2014

Thanks Tom. So I've tried that as well now and it does show that particular instance. However, it still does not provide the traversal buttons so that you can go to next and prev.

In addition - I took an extreme action to configure an entirely fresh new environment of AwareIM v5.8 and a fresh install of SQL Server 2012 in order to determine if perhaps it was an environmental situation where the self-made next/prev buttons are not working. There was no difference.