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

FORM DESIGN FOR INVOICE SET

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

    FORM DESIGN FOR INVOICE SET

    MY INVOICE HEADER TBL LOOKS UP AND FILLS IN SOME INFORMATION FROM MY CUSTOMER TBL. CUSTID LOOKS UP AND FILLS IN FIRSTNAME, LASTNAME, ADDRESS", AND A FEW OTHER FIELDS IN THE INVOICE HEADER TBL. THESE SAME FIELDS THEN POST ANY CHANGED INFORMATION BACK TO THE CUSTOMER TBL. (I HAVE RUN THIS SAME SEST OF RULES IN A5V1 WITH GOOD RESULTS). WHEN I TRY TO USE THE FORM I AM DESIGNING, IT KEEPS GIVING ME AN ERROR MESSAGE SAYING "CANNOT OPEN TABLE TO POST TO". HELP!

    #2
    RE: FORM DESIGN FOR INVOICE SET

    Mikki,

    What version are you using? Did you convert this from V1 to v4 or v4.5? If so, I believe ther xbasic between the two version has some slight differences. This might be causing your problem.

    You need to be more specific in providing details. Also, all caps make things a bit hard on the eyes, at least for me.

    kenn
    TYVM :) kenn

    Knowing what you can achieve will not become reality until you imagine and explore.

    Comment


      #3
      RE: FORM DESIGN FOR INVOICE SET

      Mikki,

      Checking the easiest thing first, make certain the customer table is in the same folder as your database, or that the path to it is correctly specified.

      How are you arranging to 'post' changes back to the customer table? Please show us the scripts and describe the events upon which you are hanging them.

      -- tom

      Comment


        #4
        RE: FORM DESIGN FOR INVOICE SET

        Hi Ken,

        I'm re-developing the application from scratch in v4.5. I'm still trying to learn xbasic, self-taught. I have it set up in the field rules for my [INVOICEHEADER->FIRSTNAME] to fill in a default value of [CUSTOMER->FIRSTNAME], customer.dbf being a child of the invoice.set. Then, I field rules set up to have the new value of [INVOICEHEADER->FIRSTNAME] to post back to [CUSTOMER->FIRSTNAME] so that if there are any changes made at the time of a sale, the customer information is kept current. It has worked well for me in A5V1, but not now.

        Comment


          #5
          RE: FORM DESIGN FOR INVOICE SET

          yes, they are in the same directory, actually the customer.dbf is a child of the invoice.set. i have them related by field rules. the invoice header has default values that fill in from the customer.dbf, then the invoice header posts any changed values back to the customer.dbf to keep customer information current. worked before in a5v1 but building this from scratch in a5v4 i get an error

          Comment

          Working...
          X