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

Hidden fields

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

  • CALocklin
    replied
    Re: Hidden fields

    Linda, someone approached me recently about starting a user group in Fenton or somewhere near there. If you are interested, send me an e-mail at CALocklin at chartermi.net and I'll get more info.

    Leave a comment:


  • CALocklin
    replied
    Re: Hidden fields

    It's been a few days but I feel strongly about this and I'm going to go along with Dave Mason.

    I never, never, never, never, never, build any application that prints forms.

    You can get away with it once in awhile - especially if printing only one record at a time. And if you can safely say that your application is complete and will not ever be modified or updated then you are probably safe. HOWEVER, my reality has always been that no application is ever complete. One of these days you are going to want to print multiple records at one time or more info on a page and then your form won't start new pages properly. Then you will end up posting another question about how to make your form print correctly and the answer will be, "You can't." At that point you will have to create a report to print your info. If the original form is basically what you want to print, the form objects can be cut and pasted to the report so it really won't take long to do.

    Another reason to keep them separate is that most screens don't have the same proportions as an 8.5x11 piece of paper. So the form on your screen can be set up so that everything is available without scrolling yet the report appears correctly on paper.

    There's short term selfishness and long term selfishness. To make things easier in the short term, print the form. To make things easier in the long run, create a report now and save yourself a bigger hassle in the future. My pappy taught me to think long term.

    Hey, I just realized that your "long term" issues are already starting - how to hide some parts of the form that you don't want printed.

    Leave a comment:


  • MikeC
    replied
    Re: Hidden fields

    Dave,
    The Richard in post #5 and #6. :)

    Leave a comment:


  • DaveM
    replied
    Re: Hidden fields

    Mike,

    What richard are you talking to??


    Linda,

    Sharing from hard experiences.

    For future, It seems much better and easier(in the long run) to use forms for input and reports for printing. Less confusion and each is generally made for the purpose.

    You can copy your form in design mode and paste it to a report as an easy step. All here will help you make the transition if you so decide.



    .

    Leave a comment:


  • MikeC
    replied
    Re: Hidden fields

    Richard,
    Exactly where I obtained the necessary syntax to do this via xbasic....never thought to tell Linda about it as I only use the Object Explorer to get the properties/syntax for the xbasic I use...not for a one time setting of properties.

    My oversight, thanks for chiming in.

    Leave a comment:


  • Mendy
    replied
    Re: Hidden fields

    In case my description wasn't clear here is screenshot.

    Leave a comment:


  • Mendy
    replied
    Re: Hidden fields

    I think I grasp what she is trying to do. I have a form I print that is bunch of check boxes with half dozen or so fields. Go to design mode, view, object explorer. Click on field in question then expand object in tree. There is option for printable. Select false and set. Worked on my form. Think you have to save first.

    Leave a comment:


  • MikeC
    replied
    Re: Hidden fields

    Not there for a field I guess...but a field object does have that property and can be set via xbasic or Action Script (AS).

    topparent:Your_Field_Name_Here.Object.Printable =.F.

    or in AS, on the left screen choose "Objects Properties (Set and Get)"...on the right screen then choose "Set Properties of Object(s)". Choose your field, then in the second box choose the Object and expand....the "printable" property can then be found.

    What event to use to place the code is very dependent upon how your form is set up to work...

    Leave a comment:


  • Linda Bronson
    replied
    Re: Hidden fields

    I'm referring to a form. I created an invoice form from the form view of the invoice table and so far it seems to be coming along well. One particular field is necessary for input, but I don't want it to appear on the printed invoice. Where would I find the logical checkbox?

    Thank you for your quick response.

    Leave a comment:


  • MikeC
    replied
    Re: Hidden fields

    Linda,
    Are you referring to a report or a form.....normally forms are not printed (reports are designed just for this, forms are not--especially a tabbed form).

    That said, there is usually a logical checkbox that allows some objects to be printed or not....a button has this for sure.

    If not a property then prior to printing you can change attributes/properties of the object/field in question to be hidden and then after printing, change back.

    Leave a comment:


  • Linda Bronson
    started a topic Hidden fields

    Hidden fields

    Is there a way to view a field for data entry purposes, but not have it appear on the printed document?
Working...
X