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

What would be the best way to "STAGE a FAKE" new record?

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

  • What would be the best way to "STAGE a FAKE" new record?

    In many apps today (or website forms) you'll notice that the fields have "greyed" fake data in the fields to tell you what needs to be input into each field. For example the First-Name field does not have a normal label but the field does have the words "First Name" in the actual field itself. As soon as you start typing to fill out the form, the fake data goes away in the field that you are editing. If you fail to fill out the field and leave it blank, the staged "hint data" re-appears.

    The other issue is I would like to do this without first creating a "real record" that might have to be deleted later if the user decides NOT to finish a valid edit. I need to do this in both the Grid mode or Detail Mode.

    How might this type of action be accomplished in A5 V11?

  • #2
    Re: What would be the best way to "STAGE a FAKE" new record?

    watermark property. ( I see you want it in grid, in dialog yes, I will check grid)
    yes it is available in grid too.
    Last edited by GGandhi; 09-11-2014, 09:11 PM.
    thanks for reading

    gandhi

    version 11 3381 - 4096
    mysql backend
    http://www.alphawebprogramming.blogspot.com
    [email protected]
    Skype:[email protected]
    1 914 924 5171

    Comment


    • #3
      Re: What would be the best way to "STAGE a FAKE" new record?

      Originally posted by GGandhi View Post
      watermark property. ( I see you want it in grid, in dialog yes, I will check grid)
      yes it is available in grid too.
      I must have seen that feature (i.e. watermark) a thousand times and never knew what it would do in a A5 app. In years of use, I never clicked on it. Thanks for the great "point in the right direction". I can't wait to try it now.

      Second point, I rarely work with dialogs and wondered is a dialog the only way to simulate a Fake Record without really creating the SQL DB blank entry? One reason is that I have created some really nice triggers that are working great and I rather not re-invent those wheels. These triggers are not an issue if I DON'T create a real record.

      Comment


      • #4
        Re: What would be the best way to "STAGE a FAKE" new record?

        Second point, I rarely work with dialogs
        why not?
        you have better control, and for data input I like dialogs, to display result I use grids. that is my style. since the dialog is stand alone not connected to a table except for binding you don't save the information till the last moment. the persistent connection is not an issue with the dialog as opposed to grids, where the grid needs to be tethered to table all the time.
        thanks for reading

        gandhi

        version 11 3381 - 4096
        mysql backend
        http://www.alphawebprogramming.blogspot.com
        [email protected]
        Skype:[email protected]
        1 914 924 5171

        Comment


        • #5
          Re: What would be the best way to "STAGE a FAKE" new record?

          Originally posted by GGandhi View Post
          why not?
          you have better control, and for data input I like dialogs, to display result I use grids. that is my style. since the dialog is stand alone not connected to a table except for binding you don't save the information till the last moment. the persistent connection is not an issue with the dialog as opposed to grids, where the grid needs to be tethered to table all the time.
          Gandhi,

          I am replying because I would like clarification on a point you made in your above response. That point was about "persistent connection". It was always my belief that a web based app only had contact with the database at those instances when an active "call" is being made. All other times, my SQL Server Express should not know anything about my connection(s) and could care even less. Unlike in my days with a product like Visual FoxPro which I believe literally kept a persistent connection to the local DBF, even though the user was sitting idle for a period of time.

          It would help tremendously if some clarity could be shared on these issues and their impact on the my current A5 V11 apps.

          Comment


          • #6
            Re: What would be the best way to "STAGE a FAKE" new record?

            I wrote a detailed example in my blog entry dated August 11th 2013. the link is at the bottom in my signature. if you like and have time take a look at that article.
            essentially the difference between dialog and grid is..

            in dialog you initiate a process of collecting data and when ready, you establish connection to the server thru your browser and deposit the information. if there are no errors, server says success if not failure and the bowser reports that back to you and the process is over and the connection is terminated. the whole thing can be repeated over and over.

            in grid you establish a connection to the server first and get some information and if you think you need to add, edit or delete some information then you do that and submit if done properly in timely manner you get success or failure the whole thing can be repeated over and over.

            so far so good, now comes the difference. it is the "timely manner". when the server sends information back it sends with a message to get any changes back and disconnects itself but the connection information is kept in the browser. when you send the correction same connection is reused. if you don't send soon the connection information is dropped by the browser ( or, say someone can close the browser and walkaway!) and you cannot send any more. so all the changes you made has to be repeated to reestablish the connection.
            to test this do the following.
            open a dialog fill in some info and take a break for half hour and come back finish rest of the information and submit.
            next open a grid update some information either in the grid or in detail and then take a break for half hour or so, comeback and update some more information and submit the changes.
            see what happens

            browser will complain that there is no active search or some thing but not in the dialog. this is also the basic nature of difference between the desktop and the web. at least in desktop you know you are always tied to the database, in web you are tied sometime or tied for a period of time. that is how web traffic is managed.

            hope this explains.
            Last edited by GGandhi; 09-12-2014, 07:10 AM.
            thanks for reading

            gandhi

            version 11 3381 - 4096
            mysql backend
            http://www.alphawebprogramming.blogspot.com
            [email protected]
            Skype:[email protected]
            1 914 924 5171

            Comment

            Working...
            X