Alpha Software Mobile Development Tools:   Alpha Anywhere    |   Alpha TransForm subscribe to our YouTube Channel  Follow Us on LinkedIn  Follow Us on Twitter  Follow Us on Facebook

Announcement

Collapse

The Alpha Software Forum Participation Guidelines

The Alpha Software Forum is a free forum created for Alpha Software Developer Community to ask for help, exchange ideas, and share solutions. Alpha Software strives to create an environment where all members of the community can feel safe to participate. In order to ensure the Alpha Software Forum is a place where all feel welcome, forum participants are expected to behave as follows:
  • Be professional in your conduct
  • Be kind to others
  • Be constructive when giving feedback
  • Be open to new ideas and suggestions
  • Stay on topic


Be sure all comments and threads you post are respectful. Posts that contain any of the following content will be considered a violation of your agreement as a member of the Alpha Software Forum Community and will be moderated:
  • Spam.
  • Vulgar language.
  • Quotes from private conversations without permission, including pricing and other sales related discussions.
  • Personal attacks, insults, or subtle put-downs.
  • Harassment, bullying, threatening, mocking, shaming, or deriding anyone.
  • Sexist, racist, homophobic, transphobic, ableist, or otherwise discriminatory jokes and language.
  • Sexually explicit or violent material, links, or language.
  • Pirated, hacked, or copyright-infringing material.
  • Encouraging of others to engage in the above behaviors.


If a thread or post is found to contain any of the content outlined above, a moderator may choose to take one of the following actions:
  • Remove the Post or Thread - the content is removed from the forum.
  • Place the User in Moderation - all posts and new threads must be approved by a moderator before they are posted.
  • Temporarily Ban the User - user is banned from forum for a period of time.
  • Permanently Ban the User - user is permanently banned from the forum.


Moderators may also rename posts and threads if they are too generic or do not property reflect the content.

Moderators may move threads if they have been posted in the incorrect forum.

Threads/Posts questioning specific moderator decisions or actions (such as "why was a user banned?") are not allowed and will be removed.

The owners of Alpha Software Corporation (Forum Owner) reserve the right to remove, edit, move, or close any thread for any reason; or ban any forum member without notice, reason, or explanation.

Community members are encouraged to click the "Report Post" icon in the lower left of a given post if they feel the post is in violation of the rules. This will alert the Moderators to take a look.

Alpha Software Corporation may amend the guidelines from time to time and may also vary the procedures it sets out where appropriate in a particular case. Your agreement to comply with the guidelines will be deemed agreement to any changes to it.



Bonus TIPS for Successful Posting

Try a Search First
It is highly recommended that a Search be done on your topic before posting, as many questions have been answered in prior posts. As with any search engine, the shorter the search term, the more "hits" will be returned, but the more specific the search term is, the greater the relevance of those "hits". Searching for "table" might well return every message on the board while "tablesum" would greatly restrict the number of messages returned.

When you do post
First, make sure you are posting your question in the correct forum. For example, if you post an issue regarding Desktop applications on the Mobile & Browser Applications board , not only will your question not be seen by the appropriate audience, it may also be removed or relocated.

The more detail you provide about your problem or question, the more likely someone is to understand your request and be able to help. A sample database with a minimum of records (and its support files, zipped together) will make it much easier to diagnose issues with your application. Screen shots of error messages are especially helpful.

When explaining how to reproduce your problem, please be as detailed as possible. Describe every step, click-by-click and keypress-by-keypress. Otherwise when others try to duplicate your problem, they may do something slightly different and end up with different results.

A note about attachments
You may only attach one file to each message. Attachment file size is limited to 2MB. If you need to include several files, you may do so by zipping them into a single archive.

If you forgot to attach your files to your post, please do NOT create a new thread. Instead, reply to your original message and attach the file there.

When attaching screen shots, it is best to attach an image file (.BMP, .JPG, .GIF, .PNG, etc.) or a zip file of several images, as opposed to a Word document containing the screen shots. Because Word documents are prone to viruses, many message board users will not open your Word file, therefore limiting their ability to help you.

Similarly, if you are uploading a zipped archive, you should simply create a .ZIP file and not a self-extracting .EXE as many users will not run your EXE file.
See more
See less

Conditional fieldrule table lookup

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Tom Stateside
    replied
    Re: Conditional fieldrule table lookup

    M. Richard,

    I'm having the same problem with conditional lookups and I'm glad you already addressed the problem in this thread. I particularly like your use of the words "enormously amateurish" to describe the appearance of the selection browse.

    Two questions.

    First, if you don't mind describing this, how would you use two separate routines with two separate lookup tables to accomplish the same thing as a conditional lookup? I'm using a field where the user makes a selection. Depending on the user's choice, one of the lookups fires. It's very simple and functions well, but is very unattractive to the end user.

    Second, do you know if v10 corrected this problem? Someone mentioned that the code for conditional lookups dates back to v1. It looks it. If v10 fixed it, that would certainly justify the upgrade.

    Thanks for your help,
    Tom

    Leave a comment:


  • M.Richard
    replied
    Re: Conditional fieldrule table lookup

    Yeah, well, you can check this out with TechSupport until you weigh an ounce, but there ain't gonna be any update to address it anymore. V10 is the word now....
    I had to abandon the conditional table lookup in the end, and work with separate embedded browses on the form, attached to separate tables. As always, a workaround was necessary and did the job.
    The conditional table lookup however did not work with saved browses whatever......

    Leave a comment:


  • robert
    replied
    Re: Conditional fieldrule table lookup

    okay, just thought I'd bring it up because it's like not being able to make a index stick in a default browse. Sounds like something to discuss with tech support.

    I didn't upgrade to 9 just because I'd have to go create a bunch of saved browses. I use conditional lookups with V8 without issue except for one type of conditional lookup that is discussed in another thread.

    Leave a comment:


  • Stan Mathews
    replied
    Re: Conditional fieldrule table lookup

    Originally posted by robert View Post
    sounds like something that should be addressed to tech support.
    No point, V9 is done.

    Leave a comment:


  • robert
    replied
    Re: Conditional fieldrule table lookup

    okay, just thought I'd bring it up. In reading, I was getting lost in whether he was using a default or saved browse. sounds like something that should be addressed to tech support.

    I didn't upgrade to 9 just because I'd have to go create a bunch of saved browses. I use conditional lookups with V8 without issue except for one type of conditional lookup that is discussed in another thread.

    Leave a comment:


  • Al Buchholz
    replied
    Re: Conditional fieldrule table lookup

    Originally posted by robert View Post
    I wonder if this is related to the change in V9 (from V8) in that you can't retain an index on a browse unless you create a saved browse.
    Robert

    I think these two issues are different....

    Leave a comment:


  • M.Richard
    replied
    Re: Conditional fieldrule table lookup

    Originally posted by robert View Post
    I wonder if this is related to the change in V9 (from V8) in that you can't retain an index on a browse unless you create a saved browse.
    That's the whole point: you can't make a saved browse and then stick it to the conditional table lookups settings...... it won't stick! It will only allow you to use the default browse.

    Leave a comment:


  • robert
    replied
    Re: Conditional fieldrule table lookup

    I wonder if this is related to the change in V9 (from V8) in that you can't retain an index on a browse unless you create a saved browse.

    Leave a comment:


  • Al Buchholz
    replied
    Re: Conditional fieldrule table lookup

    Originally posted by M.Richard View Post
    I think the "not sticking" of the specific browse in the conditional field lookup is a bug,
    I agree - I see the same thing.

    Sorry I was so dense before. Thanks for the detailed explanation...

    Leave a comment:


  • M.Richard
    replied
    Re: Conditional fieldrule table lookup

    Originally posted by Al Buchholz View Post
    There must be more to the question than what you've said.

    I don't have issues with the lookup via a default browse or saved browse..

    Are you asking about an embedded browse vs a designated browse?
    I was asking about the conditional table lookup, attached to the field rules of a table, the field to which the conditional table lookup is attached is present in an embedded browse on a form.

    So, when you 'walk' through the fields of the embedded browse on the form, the conditional lookup is triggered by a value in a previous field in the row, which fills the other fields in that row. So each row can have a different lookup table that presents the content for the rest of the fields in that browse.

    Problem is, that I do not seem to be able to let the specified browse layout in the field rules conditional lookup setting "stick". As soon as I go the the second row in the conditional table lookup settings, the entered layout for the browse to use gets blanked out again. As it defaults to the 'default browse', that seems to be the only option that works for now.

    So my question was, if you had been able at any given moment in your programming career, to get this conditional table lookup to work with specific browses attached instead of the default browse.

    I tried to disable that field rule as you suggested, but that did not work either, because when I wanted to reinstall it after saving with the option 'no lookup' it just returned the old settings, so it obviously did not delete the code when making another choice then "conditional table lookup". I remember this being a problem in other occasions as well. You think the code gets deleted, but it just is saved in the background of the module, and whenever you rechoose the option, the code just pops back up.

    Point is, that it is a whole lot of work to program this conditional table lookup by hand on the form, for instance by creating a button in a row, as opposed to simply specifying the conditional table lookup in the field rules.....
    Not to speak about the number of specific problems you will meet when trying to program it by hand.....

    So I was just wondering if you EVER got this to work with specific browses or only with default browses.

    Leave a comment:


  • Al Buchholz
    replied
    Re: Conditional fieldrule table lookup

    Originally posted by M.Richard View Post
    Do you have any experience in a conditional lookup with designated browses instead of the default one?
    There must be more to the question than what you've said.

    I don't have issues with the lookup via a default browse or saved browse..

    Are you asking about an embedded browse vs a designated browse?

    Leave a comment:


  • M.Richard
    replied
    Re: Conditional fieldrule table lookup

    Originally posted by Al Buchholz View Post
    The conditional table lookup code is very old - version 1 vintage.

    There are various problems within it, but it hasn't made the shortlist of getting fixed.

    As I recall the maintenance of multiple items has most of the problems, but if you add a new condition and provide all of the specs, it'll work. Or to change an existing condition, I've deleted the old condition and readded it..

    Since you may be doing more maintenance than not, you may want to use a different approach that may or may be workable for your app.

    Have multiple fields in the table for each condition and use a conditional object on the form to pick with field does the lookup.
    Hi Al !

    Thanx for your response.
    Your idea won't work in this particular case, since the lookup occurs on the form from within an embedded browse....
    So the lookup needs to be able to change perspective on a row base.
    Row 1, condition A is valid, the lookup enters table X
    Row 2, condition B is valid, the lookup enters table Y
    Something like that.

    I agree with you that it could very well be an issue of "sticking" changes.... I know there were more then one of those issues of changes you would make somewhere and who then (after more changes) would not "stick" at a given point.
    It is well worth a try!

    Do you have any experience in a conditional lookup with designated browses instead of the default one?

    Leave a comment:


  • Al Buchholz
    replied
    Re: Conditional fieldrule table lookup

    The conditional table lookup code is very old - version 1 vintage.

    There are various problems within it, but it hasn't made the shortlist of getting fixed.

    As I recall the maintenance of multiple items has most of the problems, but if you add a new condition and provide all of the specs, it'll work. Or to change an existing condition, I've deleted the old condition and readded it..

    Since you may be doing more maintenance than not, you may want to use a different approach that may or may be workable for your app.

    Have multiple fields in the table for each condition and use a conditional object on the form to pick with field does the lookup.

    Leave a comment:


  • M.Richard
    started a topic Conditional fieldrule table lookup

    Conditional fieldrule table lookup

    I am trying to enable a conditional table lookup on the field rules in order to conditionally determine what the lookup table should be, and then lookup the values of more then 1 field in the lookup record and copy it into the master table.

    What happens is, that you seem to be able to choose the browse to display for each table, but it does not stick!

    At the end, I can only do one of following 2:

    1- Choose for default browse on either lookup condition, that works.

    2- Choose for specific browse for 1 lookup condition, the other(s) will fail due to "browse not found" error, although specified and existing of course.

    Problem is, however the default browses work in the conditional field table lookup, you can not change the layout of those default browses and they look enormously amateurish.

    What to do?

    Using field lookup on the forum does not work either, because you can then only copy 1 field value to the master table, not for instance 5 or 6 field values in the selected record from the lookup table.

    I think the "not sticking" of the specific browse in the conditional field lookup is a bug, OR, the choice offered itself in the conditional field lookup is invalid and a bug.

    Do any of you have any experience with a conditional table lookup on the field rules, and succeeded in changing all browse layouts concerned?
Working...
X