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
Devcon 2020 Goes Virtual! LEARN MORE >

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

Read/Write in code help needed

Collapse
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
    #1

    Read/Write in code help needed

    Hi to all.
    Little help needed.
    I got:
    table called "Main.dbf" with an InvoiceId (Number) on it
    table called "InvoicesId.dbf" with an InvId field..

    I would like to enter a new record in the "Main.dbf"
    and only after saving that records fire some kind of Function or Script that :
    1-goes to "Invoices.dbf"
    2-read last record in the InvId field
    3-write that last number in the InvId field of the "Main.dbf" InvoiceId field
    4-Return to "InvoicesId.dbf" and increase the InvId

    like this i�ll have a sort of custom autonumber only if a save the record
    i�m entering.

    Some idea how to do all this in code ?

    Thanks to all

    Regards from Claudio
    Tags: None
    #2
    RE: Read/Write in code help needed

    Think this should be most of what you want. T
    his doesn't check to see what the mode of the table is when you begin the enters (could already be in enter mode).

    get pointer to "Main" table -
    tbl = table.current()

    prep variable to hold InvId -
    dim global tempinv as N

    1-goes to "Invoices.dbf" -
    tbl2 = table.open("invoices")

    2-read last record in the InvId field -
    tbl2.fetch_last()
    tempinv = InvoicesId->InvId

    3-write that last number in the InvId field of the "Main.dbf" InvoiceId field -
    tbl.enter_begin()
    main->InvoiceId = tempinv
    tbl.enter_end()

    4-Return to "InvoicesId.dbf" and increase the InvId -
    tbl2.enter_begin()
    InvoicesId->InvId = tempinv+1
    tbl2.close()
    There can be only one.

    Comment

      #3
      RE: Read/Write in code help needed

      Thanks a lot.
      I�ll try and i�ll let you know if it works.

      Regards.
      Claudio

      Comment

        #4
        RE: Read/Write in code help needed

        Thanks a lot.
        I�ll try and i�ll let you know if it works.

        Regards.
        Claudio

        Comment

          #5
          RE: Read/Write in code help needed

          I hope this is not a multi-user app or you would most likely, perforce, open the invoice table in exclusive mode (to prevent another user from deriving the same number). You would also need to check the mode of the table. If you've coded your intent (executing the procedure after saving the record), the current table will have to be put into change mode, not enter mode. Lastly, if the "exclusive open" fails on the invoice table, you've got problems since you would have saved an invoice without an invoice number (probably a primary key). If you haven't saved the current invoice, you may not be able too, until you can get exclusive access.

          This appears to be yet another attempt to maintain an unbroken consecutive numbering scheme which is simply impossible without severe data entry restrictions. There have been a lot of postings regarding this issue on the board and in the newsletter suggesting lots of nifty code and provocative work-arounds. But in the end, every method allows for gaps...in which case, why all the effort. Simply put a starting invoice number in something like a system control file which is read in exclusive mode, incremented, placed into the current invoice field, and written back to the system control file still in exclusive mode. Its fast, efficient, and simple to implement. And guess what, five of the top selling accounting packages, (MAS90, Solomon, Great Plains, Navision, Malcola) use exactly this method in a number of their modules.

          I see no particular advantage to saving a record first and then perhaps having to delete the record if the user cancels the input. Either methods will result in a gap in the invoice sequence.

          Comment

            #6
            RE: Read/Write in code help needed

            Nothing is better than a little testing-app for get the most.

            I attached a little example for you to see what happen .

            Thanks again to all.

            Regards, Claudio

            Comment

              #7
              RE: Read/Write in code help needed

              Sorry, left out

              tbl2.enter_begin()
              InvoicesId->InvId = tempinv+1
              tbl2.enter_end()
              tbl2.close()
              There can be only one.

              Comment

                #8
                RE: Read/Write in code help needed

                CV:

                I'm not good at this as you know, but here's a way that I did it.

                The 'Main' would be a one-record table. One field would hold the LAST invid number.

                The field rule for the invoice table invid would be a default or calculated value of lookupN from that 'Main' field plus 1. When the record is saved (and only then) set up a field rule post [replace] to that field changing it to the 'last saved' number. No code would be needed - all of it done in field rules.

                I'll work on an example.

                Ken

                Comment

                  #9
                  RE: Read/Write in code help needed

                  CV:

                  What I've done here might be laughable to other, more accomplished posters, but here it is.

                  Ken

                  Comment

                    #10
                    RE: Read/Write in code help needed

                    Thanks Ken,
                    as always yor tips are most functional for my apps.
                    I mean it works fine.The reason why i dont wanna use the auto increment is that if,for some reason,i empty the table,the auto increment would re-start from 1,and i think this is not good.So thanks to you,i can start over again on my app.
                    Good to "see" you again.
                    You friend Claudio.

                    Comment

                      #11
                      RE: Read/Write in code help needed

                      Good point CV, as always

                      Ken

                      Comment

                      Previous template Next
                      Working...
                      X