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



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

Message for Tom Baker

  • Filter
  • Time
  • Show
Clear All
new posts

  • Tbaker
    Re: Message for Tom Baker


    Here is a revised sample.

    Seems that Alpha has a problem in refreshing the subform. In error when I tested it this morning I was using Version 10 (which has the problem fixed). I still have to check on my home machine since I thought I was using version 9 there.

    Anyway I created a workaround for the refresh problem by putting a hidden embedded browse on the subform. Now the navigation buttons work the way they were supposed to. If there are additional invoices, the nav buttons will take you to the next invoice in order by using the hidden embedded browse which does refresh the subform. Your users will not know that this is doing since the browse is hidden. All they see is the invoice form and the nav buttons.

    Try this one.

    Let me know.

    Tom Baker

    Leave a comment:

  • Tbaker
    Re: Message for Tom Baker

    Hi Judith

    Here is a revised zip file.

    I used a subform on the bookings2 form instead of the old form fields and a dialog.

    I changed the field rules for the invref2 field in the invoice table form user entered to auto-increment and then changed the default entry in the Data Entry Tab to the next invoice number 53042.

    The subform is just the reworked Invoice_form that was used as the dialog form in the old app. I got rid of all the invoice fields in the Bookings2 form that would show if an invoice was entered - that is now the area for the subform which looks almost like it was.

    To enter a new record for the booking reference that you are viewing you would use the same new invoice button as before, however this time it will start a new invoice in the subform. To save the record entered into the subform, you would use the save record button for the parentform at the bottom. Also to Cancel a record entered into the subform before saving, use the cancel button down there also. The new record button at the bottom of the form is for entering new records into the parentform not the subform - so only use the new record button for new records into the parent form.

    Also the subform has navigation buttons on the form - they are standard First, previous, next and last buttons. This will go from invoice to invoice based on the current booking reference being viewed. If there are no more invoices and your click the next button it will put the subform into enter mode.

    See if this gives you what you want. I did this pretty fast so there are not a lot of bells and whistles but you can do that later if this works for you. Also not knowing your needs as to entering data into the invoice form, I did not do a lot of testing. Need you to do that since you will know whether it works or not for you.

    Let me know how it works for you.

    Last edited by Tbaker; 06-14-2010, 09:13 PM. Reason: another thought - Edit 2 more thoughts

    Leave a comment:

  • Peter.Greulich
    Re: Message for Tom Baker

    You could create a reverse set: Invoices 1:1 Bookings. Then you will see each invoice related to it's booking.

    Leave a comment:

  • Judith
    Re: Message for Tom Baker

    Hi Tom,

    Thanks for your reply, would I go be going along the right lines to ask if I should be using a subform so that more than one invoice can correspond to the booking.

    Leave a comment:

  • Tbaker
    Re: Message for Tom Baker


    The problem is that alpha does not know which booking reference invoice that should be shown on the form. When it was one to one, alpha matched the booking reference and would show the invoice which related to the booking reference on the form.

    I am in work right now, but will work on the app when I get home this evening (11 PM your time) and see what I can up with.


    Leave a comment:

  • Judith
    started a topic Message for Tom Baker

    Message for Tom Baker


    Tom, as mentioned in my private message to you, you very kindly helped me with a form design for raising invoices which has worked fine, but now because of raising cancellation invoices for the same booking I have had to change the link in a set from one to one, to one to many. So now when I have finished entering data into the invoice section the values disappear and it looks like there isn't a record there, but when I check the invoice table it is.