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

Prepare the app for use in network enviroment...

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

    #46
    Re: Prepare the app for use in network enviroment...

    Thanks Tim. That makes perfect sense. (And, yes, you were successful at making me feel stupid for not realizing that in the first place.)

    Comment


      #47
      Re: Prepare the app for use in network enviroment...

      Hi Tim,

      Originally posted by Tim Kiebert View Post
      ...I am quite sure that with the dbf system (as opposed to SQL) the code in the tables' field rules is run on the local machine. So if the computer times on various machines on the network are not synced to the thousandth of a second then I think it is possible to have two or more records with the same time value.
      I am 100% sure. All code is run on the local (or virtually local as in Citrix) system, which is implied in my record locking tip. The DBF server is just a dumb file/record locking and sector reading/writing daemon from the point of an A5 application. Any code is always run by the same computer as the A5 is running on (not where the EXE is located necessarily).

      Originally posted by Tim Kiebert View Post
      I do know that the now() function in a UDF records the time of the local machine. In an app I am working on that has 7 busy work stations (POS system) I have not seen an identical time but I have seen later records by record number that have an earlier time stamp. (by say a couple of minutes.)
      If your computer has a network server time, they should be within microseconds, but yes, it could happen the records still could have the same time.
      Last edited by csda1; 01-22-2012, 10:44 AM.
      Regards,

      Ira J. Perlow
      Computer Systems Design


      CSDA A5 Products
      New - Free CSDA DiagInfo - v1.39, 30 Apr 2013
      CSDA Barcode Functions

      CSDA Code Utility
      CSDA Screen Capture


      Comment


        #48
        Re: Prepare the app for use in network enviroment...

        Cal - My sincerest apologies

        Ira - thanks for upgrading my 'quite sure'. Re the network time server... I will ask the network IT guy about it.
        Tim Kiebert
        Eagle Creek Citrus
        A complex system that does not work is invariably found to have evolved from a simpler system that worked just fine.

        Comment


          #49
          Re: Prepare the app for use in network enviroment...

          Had one more question on this multi-user one to many field setups regarding auto increment fields.

          On the child field tab;e: Is it still beneficial (safer) to avoid auto-increment fields altogether, even if the linking field is something different like CTIME(NOW()) + vgUserID?

          I'm wondering whether there could be "locking" issues in a multi-user environment where parent-child tables are linked. (for example invoices, while users are adding detail records to the child table)

          I know you can use the topparent.commit() method in the invoice header, to quickly save the record (on the next line from within the script), via the button onpush event that calls calls topparent.new_record(). ~Which presumably immediately saves it before editing the rest of the fields.) But how can this be done when a user adds a new line in the detail embedded browse? (where field focus in the embedded browse controls the users action)


          Also, what are the implications when Alplha5 form mode is not set to auto? (when enter/change and view modes need to be set manually?)

          NOTE: I think I may still be a bit confused here, because it appears strange (to me) that topparent.commit() executes before user actually gets a chance to add data into the fields of the parent record. (yet this line of code is called after topparent.new_record())....

          (The order of these two commands seem asynchronous, yet they still work.)

          ie:
          line#01 topparent.new_record()
          line#02 topparent.commit()


          Line #02 appears to be fully executed before user actually enters any data in field, yet record is still saved to parent record in database....

          Maybe line #01 is instantly (immediately creating &) saving an empty record with an auto-increment field, and line #02 is merely filling in the record fields????

          PS: I'm aware of the speed benefits of not using referential integrity.
          Last edited by SNusa; 01-24-2012, 08:44 PM.
          Robert T. ~ "I enjoy manipulating data... just not my data."
          It's all about the "framework." (I suppose an "a5-induced" hard drive crash is now in order?)
          RELOADED: My current posting activity here merely represents a "Momentary Lapse Of Reason."

          Comment


            #50
            Re: Prepare the app for use in network enviroment...

            geez guys, I must be dumb.

            I learned a lot from this thread!

            I came with my own solution a long time ago and maybe luck it works or ???

            As soon as the add button is pressed, the invoice(customer ID in my case) is filled and record is saved. It is unique, of course so it checks the number as they do this. It has popped maybe 1 time in several years with 20 plus concurrent users.
            Dave Mason
            [email protected]
            Skype is dave.mason46

            Comment


              #51
              Re: Prepare the app for use in network enviroment...

              Dave, I use the same approach. Users sometimes begin a new record by mistake, but this doesn't happen often, and the unwanted record can be deleted.

              Comment


                #52
                Re: Prepare the app for use in network enviroment...

                In most of my apps, it can be deleted unlike the one with audits. I have a catchall that deletes any record without the client information in it.
                Dave Mason
                [email protected]
                Skype is dave.mason46

                Comment


                  #53
                  Re: Prepare the app for use in network enviroment...

                  Re my post above: http://msgboard.alphasoftware.com/al...l=1#post596618

                  How do you deal with detail tables, so as to guarantee no two users are adding detail auto incrementing fields at the same time?
                  (Or do embedded browses automatically handle this situation?)

                  ~Upon testing, I found that the auto-increment field (record) of the detail transactions is automatically saved as soon as the record is instantiated. (and the auto increment field is filled.) ~ I don't know how field validations & required fields effects this yet!

                  When form entry mode is set to "modeless" I tested the following:
                  Two instances of the same form are opened on the same pc.
                  Regardless of which detailed record is added, (as soon as new entry is made on child table) a record is created in the child table.
                  What is very interesting here is: It's always the first instance of the form that gets the first record added, even if the other form adds the record first!
                  Robert T. ~ "I enjoy manipulating data... just not my data."
                  It's all about the "framework." (I suppose an "a5-induced" hard drive crash is now in order?)
                  RELOADED: My current posting activity here merely represents a "Momentary Lapse Of Reason."

                  Comment

                  Working...
                  X